Chris Richardson discusses an event-driven microservice architecture, it’s benefits and drawbacks and how Spring Boot can help, implementing business logic using domain models written in Scala.
Ian Barber discusses the importance of behavior, domains and clarity of the names used when writing software or building systems.
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.
Caoilte O'Connor explains how and when the Domain Service Aggregator Archetype can help, using the architectural evolution of "Video on Demand" in a broadcast company as a working example.
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.
Volker Pacher, Sam Phillips present key differences between relational databases and graph databases, and how they use the later to model a complex domain and to gain insights into their data.
The authors share insights from their experience building DSLs for business people.
Eric Evans discusses three DDD patterns helping embedding CAP tradeoffs inside the domain model: Aggregates, Domain Events and Bounded Contexts.
Eric discusses the need for strategic thinking and how early design decisions can affect project and organization trajectories and why they involve much more than mere architecture.
Eric Evans reviews what he has learned in the 5 years since the publication of Domain Driven Design. He also describes some new patterns and talks about changes of emphasis for existing patterns.
Business users doing programming? Simonyi and Kolk presents how Intentional Software offers a radical new software approach that separates business knowledge from software engineering knowledge.
Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.