Event Sourcing your AngularJS applications
Download as PPTX, PDF2 likes1,014 views
![Maurice De Beijer [MVP], profile picture](https://cdn.slidesharecdn.com/profile-photo-mauricedb-48x48.jpg?cb=1750747544)
This document discusses data storage approaches for AngularJS applications from basic to advanced. It introduces a data storage maturity model that progresses from 0) data dump to 1) structured storage, 2) CQRS (Command Query Responsibility Segregation), and finally 3) event sourcing as the most advanced approach. Event sourcing stores all changes to data as a sequence of events and uses these events to maintain and query projections of current data states. The document encourages providing feedback on the session through a QR code and promotes joining the Microsoft Virtual Academy for free online IT training.
Event Sourcing your AngularJS applications
- 3. Who am I? • Maurice de Beijer • The Problem Solver • Freelance developer • DevelopMentor instructor • Twitter: @mauricedb • Web: http://www.TheProblemSolver.nl • E-mail: maurice.de.beijer@gmail.com
- 5. Data Storage Maturity Model 3 - Event Sourcing 2 - CQRS 1 - Structured storage 0 – Data Dump
- 6. Data Storage Maturity Model 3 - Event Sourcing 2 - CQRS 1 - Structured storage 0 – Data Dump
- 10. (Semi) Structured storage Database CRUD Server HTTP Browser
- 13. Data Storage Maturity Model 3 - Event Sourcing 2 - CQRS 1 - Structured storage 0 – Data Dump
- 14. Command Query Responsibility Segregation
- 15. Command Query Responsibility Segregation Database Query Service Browser Command Service Read Update
- 18. Data Storage Maturity Model 3 - Event Sourcing 2 - CQRS 1 - Structured storage 0 – Data Dump
- 28. Your feedback is important! Scan the QR Code and let us know via the TechDays App. Laat ons weten wat u van de sessie vindt via de TechDays App! Scan de QR Code. Bent u al lid van de Microsoft Virtual Academy?! Op MVA kunt u altijd iets nieuws leren over de laatste technologie van Microsoft. Meld u vandaag aan op de MVA Stand. MVA biedt 7/24 gratis online training on-demand voor IT- Professionals en Ontwikkelaars.
Editor's Notes
- #5: Why? I want to create better applications Most applications store the current state http://www.flickr.com/photos/celestinechua/9661913835
- #6: Levels of working with data Create Read Update Delete Command Query Responsibility Segregation Event-Sourcing
- #7: Data dumps and CRUD actions against database is very similar as seen from the front end
- #8: Most applications store the current state If you are lucky there is an audit trail of sorts http://www.flickr.com/photos/ell-r-brown/4011702143
- #9: http://www.flickr.com/photos/willowbl00/12459211923
- #10: http://www.flickr.com/photos/sukiweb/10223596316
- #11: The server is often just a simple gateway with just some validation logic
- #12: $resource and noSQL database make CRUD applications really easy
- #13: There is nothing wrong with a CRUD application if the problem domain is simple http://www.flickr.com/photos/juhansonin/5144239690
- #14: Command Query Responsibility Segregation
- #15: CQRS = Command Query Responsibility Segregation Use a different model to update information than the model you use to read information http://www.flickr.com/photos/usnavy/8220344431
- #16: Still storing just the current state Database structure is often normalized and optimized for updating Most application read far more frequently then update
- #17: Commands should be modeled after business actions A business user can understand command names and have a reasonable expectation of the outcome http://www.flickr.com/photos/micahdowty/4630801442
- #18: We are stil storing only the current state No trace of how we got there http://www.flickr.com/photos/danrocha/15602018982
- #19: Event sourcing doesn’t depend on CQRS but that structure is often used.
- #20: Event Sourcing is a very old idea that has become popular again over recent years. Events provide insight into how the system came to be in its current state http://www.flickr.com/photos/dragontomato/5174914835
- #21: Domain Event is something that has happened in the past The result of a Command to change something Very similar to the audit trail in a database http://www.flickr.com/photos/lendingmemo/11747440176/
- #22: No longer storing the current state but all event leading up to it The current state is a left fold of all events The projection parts are not really part of ES but CQRS and usually combined
- #23: Events are never erased or updated An append only model http://www.flickr.com/photos/horiavarlan/4263326117
- #24: Events are projected out to the read model Observed facts = events Derived facts = projections http://www.flickr.com/photos/fotnmc/7172465908
- #25: Eventual consistency both good and bad Better scalability Harder to program the UI Block until done Fake it on the client Use long polling or push notifications http://www.flickr.com/photos/epsos/5732013768
- #26: Event Sourcing adds complexity Don’t do it where it doesn’t make sense It’s perfectly fine to use CRUD for static reference and ES for domain in the same app http://www.flickr.com/photos/10912969@N03/2046600021/
- #27: Sample application: https://github.com/mauricedb/Movies-GES Main technologies used: https://angularjs.org/ http://geteventstore.com/ http://redis.io/ http://www.asp.net/ https://www.flickr.com/photos/kevandotorg/6229660191
- #28: More info: Martin Fowler: http://martinfowler.com/eaaDev/EventSourcing.html Greg Young: http://goodenoughsoftware.net/ Daniel Whittaker: http://danielwhittaker.me/tag/event-sourcing/ João Bragança: https://github.com/thefringeninja/derp.inventory Damian Hickey: http://dhickey.ie/?tag=/Event-Sourcing https://www.flickr.com/photos/stevendepolo/4582437563/