I've been working on an article for Kurrent / KurrentDB (formerly #EventStore and #EventStoreDB) and it is now published.
"Implementing Domain-Driven Design with KurrentDB"
https://www.kurrent.io/blog/implementing-ddd-with-kurrentdb/
I've been working on an article for Kurrent / KurrentDB (formerly #EventStore and #EventStoreDB) and it is now published.
"Implementing Domain-Driven Design with KurrentDB"
https://www.kurrent.io/blog/implementing-ddd-with-kurrentdb/
What the industry needs is an open-source high-performance Facts Record Jounal with client interfaces that are not language specific. Yes, it would support #EventSourcing, and you could call it an #EventStore, but that's too limiting.
Talk to me.
I just ported another article (from 2022) to Substack where it's not paywalled:
Advanced features of an Event Store for Event Sourcing
https://open.substack.com/pub/eventsandstuff/p/advanced-features-of-an-event-store
Just ported another article from Medium to Substack where it’s not paywalled:
„Essential features of an Event Store for Event Sourcing“
https://open.substack.com/pub/eventsandstuff/p/essential-features-of-an-event-store?r=4t477p
A wave of relief washes of me as I shut down the #eventstore cluster. I find some weird kind of closure as 6 years of trauma inducing engineering come to an end.
EventStore cannot hurt me anymore.
I just published the follow-up article:
"Advanced features of an Event Store for Event Sourcing"
https://medium.com/@TonyBologni/advanced-features-of-an-event-store-for-event-sourcing-a457ebd77692
Mastodon first, the bird site and others will have to wait. ;-)
Boosts are highly appreciated! 🙏 💛
@oskardudycz @yellowbrickc @jkonecki @gunnarmorling @[email protected] @trondhjort @MarkusG @alexzeitler @dairyleia
Here we go, new article "Essential features of an Event Store for Event Sourcing"
https://medium.com/@TonyBologni/essential-features-of-an-event-store-for-event-sourcing-13e61ca4d066
There will be a second part very soon:
"Advance features ..."
Already finished, I split it, because it was 14 minutes reading time, which is a bit long.
Just writing an article
„Essential features of an event store“
Played with ChatGPT to create a list of requirements. Just for fun, I know the topic well enough to beat the AI (Dunning Kruger?).
Please comment, if you like:
What do you think are those _essential_ features?
Maybe I missed something (I‘ll not anchor you with my list!).
(rewrote because v1 sucked @yellowbrickc)
As @yellowbrickc notified me that it did not come clear that this is a
Request For Comments ->
Please comment if you think I missed some essential point!