When, why and how to CQRS

Key takeaways
  • You will learn about event sourcing
  • You will learn how to model business transactions without locking the whole world.
  • You will see why the real world acts as a good example for eventual consistent use-cases.
  • You will see Java EE with Apache Kafka and Docker in action.

Most of today’s enterprise applications base on a CRUD data model that is simple and straightforward to implement. Another concept of how to model applications is Command Query Responsibility Segregation (CQRS) that enables interesting solutions and use cases, especially with rising demands of scalability.

In this session I’ll show the concept and benefits of CQRS, to which other buzzwords such as eventual consistency, event-driven architectures and event sourcing it is related and how to realize a CQRS application. The questions whether this concept can be realized with Java EE technology, where the framework already offers solutions and where it has to be extended will be answered. Most of the time will be spent live-coding and examining the “devil is in the details” cases of both approaches.

addremove Add to schedule

Other sessions - Sebastian Daschner


Best companies