Please log in to watch this conference skillscast.
Most React-Redux applications just store the work in progress as is in a database. It is fine to treat data in a simple CRUD fashion like this with a smaller application. But yet this is not optimal when applications get more complex. Use the Command Query Responsibility Segregation (CQRS) design pattern for more complex applications. More so, combining this with Event-Sourcing (ES) is an even more powerful solution. Further, Event-Sourcing ensures that every action, which led up to the current state, is stored as a separate domain event.
This collection of domain events is then used as the write model in the CQRS model. These same events are then launched into a secondary database to build the read model for the application. During this session, Maurice de Beijer explains why you might want to use Event-Sourcing. He further explains how to get started with this design in your React and Flux applications.
YOU MAY ALSO LIKE:
- The JVM as a platform for building smart contracts (in London on 28th June 2017)
- London Microservices User Group- July (in London on 5th July 2017)
- Infiniteconf 2017 - the conference on Big Data and Fast Data (in London on 6th - 7th July 2017)
- Uncle Bob's Advanced TDD (in London on 30th - 31st October 2017)
Event-Sourcing your React-Redux applications