Last year (2018) I worked on a project for which we thought Domain-Driven Design would be a perfect match, because we really needed to engage our users as early as possible during development. Additionally we had some technical requirements for which CQRS and Event Sourcing also seemed like a good match.

During this talk I will explain why we thought this was, how we implemented this with the help of Prooph components, what kind of problems we ran in to, and how we solved them.

My talk is divided into the following parts:

- Brief explanation of the project and its requirements on a functional level (what it should do, target audience, etc; non-commercial)
- Why we thought Domain-Driven Design would be a perfect match
- Brief explanation of CQRS and Event Sourcing
- Outline of the available Prooph components (what they are/do, and which ones we decided to use)
- Code examples (small) of how we implemented this in the project
- How it performed in the production environment, which problems/complexity we had to face, and how we solved that (mostly back-end, but also front-end)

This talk is aimed at Intermediate, but it can be turned into an Advanced talk by shortening the DDD, CQRS and Event Sourcing explanations, and showing more code of how we fixed the problems we faced. Additionally I can provide more details about the architecture that was used in production.

It is mainly focused on development in general, but also includes the following categories:

- APIs (REST)
- Databases
- Frameworks (we used Symfony 4 and Prooph combined)
- JavaScript