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:
- Greg Young's CQRS, Domain Events, Event Sourcing and how to apply DDD (in London on 18th - 20th October 2017)
- ReactiveConf (in Bratislava on 25th - 27th October 2017)
- Damjan Vujnovic's Reactive Programming Workshop (in London on 27th - 29th November 2017)
- Fast Track to React (in London on 22nd - 23rd January 2018)
Event-Sourcing your React-Redux applications