LocalDTO
martinfowler.com · 562 words · saved by 1 readers
a bliki entry for LocalDTO
If you've been keeping an eye on my fellow ThoughtBloggers you'll know that it seems one of my fowlbots has blown a fuse, the Australian sun obviously frizzles these Swedish models. Jon's annoyed with Data Transfer Objects, but it's not that DTOs are a bad thing, just like any pattern they are useful in a certain context. Patterns always have two parts: the how and the when. Not just do you need to know how to implement them, you also have to know when to use them and when to leave them alone. He does have a point - although I only talk about them in the context of remote interfaces, I…
saved by
related reading
- Everything I know about good system designseangoedecke.com
- Building a BFT JSON CRDTjzhao.xyz
- The Law of Leaky Abstractions – Joel on Softwarejoelonsoftware.com
- Notes on Distributed Systems for Young Bloods – Something Similarsomethingsimilar.com
- The Wrong Abstraction - Sandi Metzsandimetz.com
- Everything I know about good API designseangoedecke.com
- An Interactive Intro to CRDTs | jakelazaroff.comjakelazaroff.com
- Local, first, forevertonsky.me
- Data Laced with History: Causal Trees & Operational CRDTs — Archagon Was Herearchagon.net
- The subtle beauty of Durable Objects, and what could be better about them / Moment devlogmoment.dev
- How to write complex softwaregrantslatton.com
- Destroy All Values: Designing Deinitialization in Programming Languages - Faultloregankra.github.io