Thank you!

I think the event-sourcing pattern is still less studies and less widely used than “normal” CRUD applications. What follows, is that there’s less tooling, libraries, frameworks and best-practices. Which might be one of the reasons people are cautious when adopting the pattern.

That said, I don’t see why you couldn’t adopt it across the board. Though I can imagine that you could also have some fast-changing data where you don’t want to keep the audit, for example. So it’s good to keep things flexible and pick ES/CRUD depending on the needs. But ES might be a good default.

--

Software engineer, Functional Programming and Scala enthusiast, SoftwareMill co-founder

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Adam Warski

Adam Warski

Software engineer, Functional Programming and Scala enthusiast, SoftwareMill co-founder