Chris Richardson describes how to implement business logic using a domain model that is based on event sourcing. He compares and contrasts a hybrid OO/FP design with a purely functional approach.
Alberto Brandolini discusses how the Theory of Constraints, Kanban, CQRS, Domain-Driven Design, EventStorming and UX blend together to solve the real problems in software development.
Udi Dahan takes a look at why different kinds of pub/sub need to be used for specific domains like healthcare, finance, “internet of things”, and some kinds of retail.
Eric Evans discusses how to create good or even great designs with DDD without attempting to be perfect.
Mike Barker shares lessons learned at LMAX Exchange: starting from a clean domain model is imperative and understanding the trade-offs between performance and safety/generality/functionality.
Eric Evans shares approaches that have helped him with issues in architecture, with a focus on establishing boundaries between software with different conceptual approaches and discipline levels.
A lively panel discussion with Eric Evans, Duncan DeVore, and Leo Gorodinski, hosted by Mike Feathers, on software architecture improvement, DDD, the ins and outs of microservices and much more.
Amit Rathore shares advice in building large scale applications in Clojure, making sure the code is readable and maintainable.
Eric Evans discusses three DDD patterns helping embedding CAP tradeoffs inside the domain model: Aggregates, Domain Events and Bounded Contexts.
Robert Reppel discusses applying DDD and SOLID techniques in order to improve legacy code, exemplifying with real code.
Eric Evans shares 4 strategies for dealing with messy legacy systems: Bubble Context, ACL Synchronization, Exposing Legacy Assets, and Domain Events Channel.
Oliver Gierke demoes using Spring Data JPA to create repositories using a Domain-driven Design approach.