Greach 2014, The Groovy Spanish Conf 28/March, Madrid, Spain
http://greach.es
Follow us on twitter
http://twitter.com/greach_es
Slides and demo source code in:
http://greach.es/speakers/steve-pember-richer-data-history-in-grails-with-event-sourcing/
As Grails developers we tend to reflexively lean on creating a pattern wherein a single Domain Object maps to one (or many related) rows in a relational database. This row represents the current state of the object in our system after some transaction or operation has been performed on it and this will typically be just fine. But what if we want to know WHY the Domain Object is in it's current state? How did it get there?
Enter Event Sourcing: instead of persisting the current state of our Domain Objects, we store historical events about them. In this talk I will discuss the basic concepts of Event Sourcing. We will discuss the advantages--particularly around performance and analytics--and disadvantages of using this pattern. We will see how easily it can be implemented in Groovy and used within a Grails application. Finally, we'll examine some practical use cases and when one would consider implementation.
Steve Pember
Principal Consultant with Cantina
Steve is a Principal Consultant with Cantina -- a technology agency in Boston, MA, USA -- which specializes in utilizing the forefront in web technologies to construct top-notch web experiences. His passion lies in architecting and developing performant, scalable, full-stack systems for the web. He an avid fan of the Groovy language, is a past speaker at GR8Conf, and organizes the Boston Grails/Groovy User Group.