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
- Rhizome Proposaljzhao.xyz
- Best Practice - An Introduction To Domain-Driven Design | Microsoft Learnlearn.microsoft.com
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- The Distributed Computing Manifesto | All Things Distributedallthingsdistributed.com
- Clean Coder Blogblog.cleancoder.com
- endtoend.pdfweb.mit.edu
- Tao of Node - Design, Architecture & Best Practices | Alex Kondovalexkondov.com
- Presentation Domain Data Layeringmartinfowler.com
- Modular data modeling techniques with dbt | dbt Labsgetdbt.com
- Analytics Corner - 3. Basic Modelingdrexel-uhc.github.io
- The subtle beauty of Durable Objects, and what could be better about them / Moment devlogmoment.dev
- What is Jazz?jazz.tools