Routing Patterns

At its core, Redux is all about actions that change the state. Although its architecture wasn’t directly inspired by the concepts of event sourcing and the command-query separation principle, Redux’s fundamentals are close and allow us to use existing principles and patterns to handle side effects.

There are two main types of messaging patterns to consider when working with Redux: routing patterns and transformation patterns.

You can find more information on the patterns described here and others in the great book Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf.

Routing patterns

Technically speaking, we use routing patterns to decouple a message’s source from the message’s ultimate destination. To simplify, we use patterns to determine which side effects are triggered in response to actions. Let’s take a look at some common routing patterns:

Filter