Saying redux is like event sourcing, is like saying redux is like a state machine. It's definitely possible to model redux like a state machine, but there's no inherent constraint in redux that promotes this.
The only constraint redux has is that reducers are pure...there's no constraint on actions. Actions can be modeled as commands or events.
Then again, if they're events, where are the commands? And if they're commands, where are the events?
Also where is CQRS? Aggregates?
"Event-driven" does not mean "event sourcing".
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Saying redux is like event sourcing, is like saying redux is like a state machine. It's definitely possible to model redux like a state machine, but there's no inherent constraint in redux that promotes this.
The only constraint redux has is that reducers are pure...there's no constraint on actions. Actions can be modeled as commands or events.
Then again, if they're events, where are the commands? And if they're commands, where are the events?
Also where is CQRS? Aggregates?
"Event-driven" does not mean "event sourcing".