Domain-driven design (DDD) is helpful for managing complex processes and rules—especially those between business experts and developers/users—and turning them into models. 

CEO of Virtual Genius Paul Rayner describes how the vast tooling in DDD enables developers to focus on the coding that really matters and makes systems more collaborative, taking into account three primary considerations: (1) how to get better at collaborating, (2) strategic design and understanding why design really matters, and (3) modeling codes. He also touches on bounded context, microservices, event storming, event sourcing, and the relationship between Apache Kafka® and DDD.  

EPISODE LINKS

• What is Domain-Driven Design?
• Microservices, Apache Kafka, and Domain-Driven Design
• Turning the Database Inside Out with Apache Samza
• Let’s Build “eBay” by “Turning the Database Inside Out” and Using Serverless
• Designing Event-Driven Systems
• Design Patterns: Elements of Reusable Object-Oriented Software
• The Event Storming Handbook
• Refactoring: Improving the Design of Existing Code
• Explore DDD Conference
• Join the Confluent Community Slack