Hello everyone! In today’s video I would like to explain how event sourcing is actually implemented, using the code I’ve been recently working with as an example. Here I’m focusing not so much on business logic but rather on the patterns required to build objects from events and to change objects before publishing new events. I’m also talking about the decision-making process and manipulation of states. Although this approach takes some time getting used to, implementing aggregates is relatively easy.
You can find more information of this topic in two blog posts linked down below:
https://blog.arkency.com/one-simple-t...
https://blog.arkency.com/event-sourci...
*****
Find more:
➡ Andrzej Krzywda on Twitter: / andrzejkrzywda
➡ Andrzej Krzywda on Instagram: / andrzejkrzywda
📖 Domain-Driven Rails: https://blog.arkency.com/domain-drive...
📖 Fearless Refactoring: Rails Controllers https://rails-refactoring.com/
📖 Frontend-friendly Rails: https://blog.arkency.com/frontend-fri...
📖 React.js by Example: https://reactkungfu.com/react-by-exam...
📖 Rails Meets React.js: https://blog.arkency.com/rails-react/
📖 Asnyc Remote: https://blog.arkency.com/async-remote/
📖 Responsible Rails: Trustworthy Developers: https://blog.arkency.com/responsible-...
📖 Blogging for Busy Programmers: https://blog.arkency.com/blogging/
➡ Arkency Website: https://arkency.com/
➡ Arkency Blog: https://blog.arkency.com/
➡ Arkency on Twitter: / arkency
➡ Arkency on Facebook: / arkency.com
➡ Arkency on LinkedIn: / arkency