All the cool kids...
summary
Covers concrete claims and patterns: Domain‑Driven Design drives ubiquitous language and bounded contexts; Behavior‑Driven Development uses given-when-then examples and tools like Behat to make acceptance tests executable; CQRS plus event sourcing writes every change as an append‑only event store so projections build fast read models and streams are replayable for analytics; microservices accept commands, emit events, and keep decentralized data. Mentions 225 noSQL databases as a historical note and runs for about 40 minutes.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:02Conclusion: Use "cool" things when you understand them
- 2:58Conclusion: Use "cool" things that last
- 3:14Not what this talk is about
- 4:21Serious psychological Impediments
- 17:13What's the next most important thing the system doesn't do?
- 19:52BDD is an agile methodology for creating software that matters
- 21:25Design your domain model guided by examples
- 24:35About CQRS and Event Sourcing
- 26:54Domain events!
- 43:26Implementing Domain Driven Design (Vaughn Vernon)
related talks
37mBuilt to last: A domain-driven approach to beautiful systems
39mDomain-Driven Design: Hidden Lessons from the Big Blue Book
38mDomain-Driven Design: Hidden Lessons from the Big Blue Book
01h 05mDDD, event sourcing and CQRS – theory and practice
59mDomain Driven Design: The Good Parts
50mIt's All About the Domain, Honey - Domain-Focused Architecture with DDD
01h 11mAn introduction to DDD
50mDomain Driven Design in Cloud Native Environments