Apply DDD/CQRS/ES to your domain!

Today we’ll deep dive into ubiquitous language, business domains and bounded contexts. As an example, we’ll eventstorm and design a hotel reservation system. The goal is to have well-defined events, commands and aggregates, expressed in business terms, scoped to reflect business priorities and objectives.

Like other practices, applying undistracted attention to your domain takes years to hone. Instead of traditional user story mapping, we'll be using Event Storming to explore the goals and mechanics of a solution. With the proper abstractions in place, the next steps in organizing your solution for scalability becomes clear - how does the CAP Theorem affect your solution?

At this meetup we'll take on any example domains or work on open-source projects where this can be explored. Focus can shift from Domain Driven Design to Command Query Responsibility Segregation to Event Sourcing - depending on who's attending that day.

There's a handful of experienced practitioners in town, and you can find them here to help you understand this excellent approach to building software.