jdumont
So…I’m back in front of a text editor (and not behind a camera) and this cropped up just as I logged into the forum again after — checks calendar — a solid 18 months away! I’ve switched careers but still plan to do some software here and there, mainly building out ideas for myself and those close to me.
One idea would suit ES, but some time away has provided a bit of clarity. Why use event sourcing when it’s a pattern that requires a lot of ceremony and almost always come with CQRS which can be a burden, even just from deployment costs for a zero-income idea.
I’m now wondering if I could simply design my database architecture in a way that captures changing data, rather than just throwing away the old. Querying current data would require a more complex join (perhaps finding the latest version of some fields, rather than having the current data denormalised on the read side of CQRS).
In short, how much value do you feel event sourcing offers, versus simply designing your database in such a way that data isn’t thrown away?
Where Next?
Trending in Discussions
Other Trending Topics
Chat & Discussions>Discussions
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
hst337
Event sourcing is not just about persisting all application state changes. Event sourcing is about linearization of events and reproducibility of state changes, which is useful only in some parts of the system (like something related to money or extremely secret data). This approach must not be used for all entities and events in the system.
To persist all entities (even changed or deleted ones), you can simply use
deletedboolean column (which is common, but not recommended) or have the clone for each table just in another schema.tcoopman
On mobile so need to keep this short.
An other place where event sourcing shines is when there is a temporal aspect in your problem space. If you only have crud operations ES will not offer a lot of value.
On the other hand. If you need to model complicated processes ES can deliver!
It’s true that ES might require different architectural design (different but more). That’s definitely something too consider but if you model only some entities with ES you might not need that.
thojanssens1
could you clarify why it’s ideal for secret data?