Domain Driven Design: The Good Parts - Jimmy Bogard
The greenfield project started out so promising. Instead of devolving into big ball of mud, the team decided to apply domain-driven design principles. Ubiquitous language, proper boundaries, encapsulation, it all made sense.
But along the way, something went completely and utterly wrong. It started with arguments on the proper way of implementing aggregates and entities. Arguments began over project and folder structure. Someone read a blog post that repositories are evil, and ORMs the devil incarnate. Another read that relational databases are last century, we need to store everything as a stream of events. Then came the actor model and frameworks that sounded like someone clearing their throat. Instead of a nice, clean architecture, the team chased the next new approach without ever actually shipping anything.
Beyond the endless technical arguments it causes, domain-driven design can actually produce great software. We have to look past the hype into the true value of DDD, what it can bring to our organizations and how it can enable us to build quality systems. With the advent of microservices, DDD is more important than ever - but only if we can get to the good parts.
NDC Conferences
https://ndcsydney.com
https://ndcconferences.com
Видео Domain Driven Design: The Good Parts - Jimmy Bogard канала NDC Conferences
But along the way, something went completely and utterly wrong. It started with arguments on the proper way of implementing aggregates and entities. Arguments began over project and folder structure. Someone read a blog post that repositories are evil, and ORMs the devil incarnate. Another read that relational databases are last century, we need to store everything as a stream of events. Then came the actor model and frameworks that sounded like someone clearing their throat. Instead of a nice, clean architecture, the team chased the next new approach without ever actually shipping anything.
Beyond the endless technical arguments it causes, domain-driven design can actually produce great software. We have to look past the hype into the true value of DDD, what it can bring to our organizations and how it can enable us to build quality systems. With the advent of microservices, DDD is more important than ever - but only if we can get to the good parts.
NDC Conferences
https://ndcsydney.com
https://ndcconferences.com
Видео Domain Driven Design: The Good Parts - Jimmy Bogard канала NDC Conferences
Показать
Комментарии отсутствуют
Информация о видео
Другие видео канала
Six Little Lines of Fail - Jimmy BogardDDD and Microservices: At Last, Some Boundaries!What is DDD - Eric Evans - DDD Europe 2019Greg Young — A Decade of DDD, CQRS, Event SourcingCreating event-driven microservices: the why, how and what by Andrew SchofieldEric Evans — Tackling Complexity in the Heart of SoftwareClean Coders Hate What Happens to Your Code When You Use These Enterprise Programming TricksFour Languages from Forty Years Ago - Scott WlaschinGreg Young - The Long Sad History of MicroServices TMDDD & Microservices: At Last, Some Boundaries! • Eric Evans • GOTO 2015The Many Meanings of Event-Driven Architecture • Martin Fowler • GOTO 2017Avoiding Microservice Megadisasters - Jimmy BogardDomain-Driven Refactoring - Jimmy Bogard - NDC Oslo 2020Slice & Dice your Monolith with Domain Driven Design by Edson YanagaVertical Slice Architecture - Jimmy BogardDeveloping microservices with aggregates - Chris RichardsonFrom SQL to Azure Cosmos DB - Jimmy Bogard3. DDD Strategic Design in under 15 minutesDesign Microservice Architectures the Right Way