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:
- FullStack Event Sourcing and Applied DDD with Roman Sachse (Online Course on 23rd - 25th September 2020)
- Domain Models in Practice: DDD, CQRS & Event Sourcing with Marco Heimeshoff (Online Course on 28th September - 2nd October 2020)
- Applied Domain-Driven Design — Full-Stack Event Sourcing (SkillsCast recorded in July 2020)
- First look at Jetpack Compose (SkillsCast recorded in October 2019)
Event-Sourcing your React-Redux applications