〈Kafka가 이벤트 스토어로 적합하지 않은 이유〉 — Anton Stöckl

https://itnext.io/event-sourcing-why-kafka-is-not-suitable-as-an-event-store-796e5d9ab63c

이벤트 소싱, Kafka의 특성과 적합한 분야에 대해 공부하고 다시 생각하는 계기가 되었다.

#eventsourcing #eventstore #kafka #cqrs

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.

#eventsourcing #eventstore

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 @togetherwecode @trondhjort @MarkusG @alexzeitler @dairyleia

#EventSourcing #eventstore

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.

@oskardudycz @yellowbrickc @jkonecki

#eventsourcing #eventstore

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!

#eventsourcing #eventstore

And it's funny that @adymitruk faved this just now because something I completely forgot -- our app is also using #EventSourcing! Considering that a huge win, especially because I had to teach it to a new team, learn some things myself, and we were locked into #SQLServer so didn't have the "easy paths" available to us like #Marten or #EventStore.

I built a very similar system, on top of @PostgreSQL@twitter.activitypub.actor, for the SaaS version of http://Mercure.rocks, and so far it works amazingly well. I’m glad to see an open source tool implementing the same idea.
---
RT @glaforge@twitter.activitypub.actor
"Announcing Message DB: Event Store and M@PostgreSQL@twitter.activitypub.actore for PostgreSQL"

Like #kafka and #EventStore but lighter (only key features), and built atop …
https://twitter.com/glaforge/status/1207335469937246216

RT @glaforge@twitter.activitypub.actor
"Announcing Message DB: Event Store and Message Store for PostgreSQL"

Like #kafka and #EventStore but lighter (only key features), and built atop #PostgreSQL

Provides Pub/Sub, JSON metadata, event streams, message queue and storage.
https://buff.ly/2PvaF70