Most applications only know the present. Their current state is calculated and updated somewhere on every change, effectively losing any previous states and information that only existed in the past. Can that be a limitation? Missed opportunity? What if your application could remember its entire history? Would that be any helpful, or is it a worthless effort? This talk will provoke Java developers to start asking such questions. It will provide useful mental models to better understand Event Sourcing, DDD, and CQRS concepts. It will also demonstrate what it takes to build such applications in Java.
Objective of the presentation:
To provide applicable mental models to understand better the Event Sourcing architectural pattern and to demonstrate how painlessly do it in Java applications
Attendee pre-requisites - If none, enter "N/A":
N/A