Event-Sourcing your React-Redux applications
•Download as PPTX, PDF•
0 likes•1,869 views
![Maurice De Beijer [MVP]](https://cdn.slidesharecdn.com/profile-photo-mauricedb-48x48.jpg?cb=1696317804)
This document discusses event sourcing for React-Redux applications. It introduces event sourcing and how it can be used to store application data and state changes as a sequence of immutable events. It describes using event sourcing with projections to update views and using command and query services to write events to the database and read/update projections. It provides examples of implementing event sourcing for a permit collection reducer and connecting the state to React components.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Event-Sourcing your React-Redux applications
Similar to Event-Sourcing your React-Redux applications (20)
More from Maurice De Beijer [MVP]
More from Maurice De Beijer [MVP] (20)
Recently uploaded
Recently uploaded (20)
Event-Sourcing your React-Redux applications
- 1. Event-Sourcing your React- Redux applications Maurice de Beijer - @mauricedb
- 2. Who am I? • Maurice de Beijer • The Problem Solver • Microsoft Azure MVP • Freelance developer/instructor • Twitter: @mauricedb and @React_Tutorial • Web: http://www.TheProblemSolver.nl • E-mail: maurice.de.beijer@gmail.com
- 9. (Semi) Structured storage Database CRUD Server HTTP Browser React
- 11. A React component to display data
- 12. Command Query Responsibility Segregation
- 14. Command Query Responsibility Segregation Database Query Service Browser React Command Service Read Update
- 16. A Redux Action Creator
- 27. The permit collection reducer
- 28. The single permit reducer
- 29. The React application startup
- 30. Connecting the state to the component
- 31. Maurice de Beijer - @mauricedb
Editor's Notes
- Why? I want to create better applications Most applications store the current state http://www.flickr.com/photos/celestinechua/9661913835
- Deepwater Horizon Offshore Drilling Platform on Fire https://www.flickr.com/photos/ideum/4711481781
- 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
- http://www.flickr.com/photos/willowbl00/12459211923
- http://www.flickr.com/photos/sukiweb/10223596316
- The server is often just a simple gateway with just some validation logic
- There is nothing wrong with a CRUD application if the problem domain is simple http://www.flickr.com/photos/juhansonin/5144239690
- A basic React component to show a list of permits
- 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
- 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
- Still storing just the current state Database structure is often normalized and optimized for updating Most application read far more frequently then update
- The JavaScript command to send to the server
- Using Flux Standard Actions
- We are still storing only the current state No trace of how we got there http://www.flickr.com/photos/danrocha/15602018982
- Event Sourcing is a very old idea that has become popular again over recent years. Invented by Greg Young Events provide insight into how the system came to be in its current state The current state is a left fold of the events http://www.flickr.com/photos/dragontomato/5174914835
- https://www.flickr.com/photos/eisenbahner/4051462178/
- 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/
- Invented by Greg Young 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
- Another service subscribes to the same events And pushes them to each connected client
- Flux has a very similar and explicit way of working with data.
- Events are projected out to the read model Observed facts = events Derived facts = projections http://www.flickr.com/photos/fotnmc/7172465908
- https://en.wikipedia.org/wiki/File:Mercator_projection_SW.jpg
- https://en.wikipedia.org/wiki/File:Mollweide_projection_SW.jpg
- A Redux reducer function for a collection of permits. It calls another reducer for individual permits Very functional: Old State + Action = New State
- A Redux reducer function for a single permit.
- The Redux createStore() function creates the store based on the reduce functions. The React-Redux Provider connects the store state to the root App component.
- The React-Redux connect functions makes data from the store available as props for the child React component.
- More info: Greg Young: http://goodenoughsoftware.net/ Martin Fowler: http://martinfowler.com/eaaDev/EventSourcing.html 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/