Event-Sourcing your React-Redux applications

13th July 2016 in London at CodeNode

There are 85 other SkillsCasts available from FullStack 2016 - the conference on JavaScript, Node & Internet of Things

Please log in to watch this conference skillscast.

581414710 640

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.


Event-Sourcing your React-Redux applications

Maurice de Beijer

Maurice de Beijer is an independent software consultant and trainer. He specializes in JavaScript, React, AngularJS and ASP.NET MVC. His work includes a large, global, safety application for the oil and gas industry. Maurice is also active in the open source community. He teaches ECMAScript, TypeScript, React, Angular JS and ASP.NET MVC courses. Since 2005, he has received Microsoft’s Yearly Most Valuable Professional Award. Further, Maurice is active in the Dutch dotNED user group and organizes it meetings.