CQRS / Event sourcing
Details
Hi Devs !!! we are in the road again :)
This time hosting an event about "CQRS / Event Sourcing" next Thursday 10th of Novembre at the Netcentric offices.
CQRS (http://martinfowler.com/bliki/CQRS.html) stands for Command Query Responsibility Segregation. The idea behind is to split the conceptual model into separate models for update and display, which it refers to as Command and Query respectively following the vocabulary of CommandQuerySeparation. The rationale is that for many problems, particularly in more complicated domains, having the same conceptual model for commands and queries leads to a more complex model that does neither well.
Adrian is a seasoned software developer having worked 16+ years in designing and implementing enterprise solutions in large scale projects.
His expertise includes strong hands-on technical skills with Enterprise Applications based on JEE technology, in Enterprise Integration area, database development, object oriented analysis/design, data modeling and client/server application development. In the last years he has been working on a service design platform where he applied CQRS architectural principles.
In this talk he will give us a deep dive into the CQRS / Event Sourcing architectural principles with an example implementation in Scala and Akka Persistence backed up by Cassandra for event journaling and Titan for snapshot persistence.
Adrian Florea
Software architect
Java & Scala Developer
https://www.linkedin.com/in/acflorea
CQRS / Event sourcing