Modeling complex problems is hard and often leads to very complicated code. Controllers, repositories, services, conditions, forms - client’s business requirements sometimes infiltrate all these layers, everything is mixed together, making code really difficult to read, understand and develop. When you want extend business logic, but you need to dig in tens (or even hundreds) lines of controller action, trying to understand what are all these objects for and what other places should be changed too, it’s time to try different approach… "Thinking in events" means that you can be fully focused on problem domain, implementing testable business logic and associated rules, not on database, web framework or other implementation details. During this workshop you will learn how to use event/command buses in your app, apply Event Sourcing to store all history or split reads from writes with CQRS to increase performance, scalability and security. Being concentrated on client real problem the same time, without any distractions from code.


Comments are closed.

Martijn Smit at 14:49 on 30 Jun 2017

Very nice tutorial. Learned alot about event driven development.

Tim Huijzers at 12:21 on 3 Jul 2017

Very useful to finally get some insite in event sourcing. Only thing I'm missing is the integration in framework of application

Anonymous at 13:31 on 3 Jul 2017

Nice workshop, some concepts became much clear for me. And I know how I can use them in my setup. I really appreciate discussions and hints during the breaks, thanks for that. Maybe some of these discussions should be public, as an improvement for next workshop.