DDD: Designing & Implementing Aggregates and Read Models

A closer look at aggregates, transactional scope, read models and why they matter a lot when implementing "microservices". Last week we explored events, commands, bounded contexts and domains in a fictitious hotel management system. Today we'll derive aggregates, read models and services for one of the three contexts we identified - the Online Booking System. Code examples can be found here: https://github.com/robertreppel/eventsourcing-hotelreservations

About this group:

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.