DomoTacticalStorage-TS is now available for #ActorModel.

Persistent storage backends for DomoTactical-TS providing #EventSouring Journal and DocumentStore implementations for #Kurrent #KurrentDB / #EventStoreDB and @cloudflare #D1.

https://www.npmjs.com/package/domo-tactical-storage

I just had a conversation about the #EventStoreDB reboot now known as #Kurrent (formerly Event Store). Thanks, Holden Ackerman, for conveying the fresh vision that goes well beyond immutable event logs and projections.

Would your enterprise be better off with discreet records for everything that happened in your system?

So I just casually merged such a small Pull Request extending „a bit” my workshop exercises in #Java.

https://github.com/oskardudycz/EventSourcing.JVM/pull/58

Wanna see how to implement event stores on top of #PostgreSQL or #Mongo? How to use #EventStoreDB? Why not!

I’m going to have a few open and private workshops teaching #EventSourcing in practice. You can also join them or schedule one.

Or, you can try to do exercises as a self-paced kit, as I’m always open sourcing all of them. That’s not the full workshop experience, but can be good enough 🙂

Regular expressions are one of the classic examples of hate and hate relationships. Yes, it’s not a typo; hate and hate. Do you know anyone who loves or knows how to write moderately complex regex?

Still, undeniably, regular expressions are useful and powerful.

In my recent article, I showed an example of using Regular Expressions to filter #EventStoreDB subscriptions by event types. That helps to more efficiently get notifications about new events.

https://event-driven.io/en/filtering_eventstoredb_subscriptions_by_event_types/

I'm not sure how far this #emmett will go, but I already like that it looks like a real project. The quality and test improvements, CI, and CD setup. Thiago's PR is a good example of it. It shows how to set up the matrix tests for multiple event store implementations. Currently, we have #EventStoreDB and in-memory, but having a test matrix upfront will speed up adding new storage.

2/

I’m on the market for a staff/principal role. I have a passion for #SoftwareArchitecture, Developer Experience, community, mentoring, #performance, and interacting with business and domain experts.

Comfort zone: #php #typescript #react #symfony #laravel

Excited about: #eventsourcing #eventsauce #eventstorming #domaindrivendesign #modeling

Would love professional exposure to: #kotlin #golang #dotnet #python #eventstoredb

Visit beausimensen.com to contact or DM me.

#FediHire #GetFediHired

Yesterday, I bragged about my #EventSourcing samples for #dotnet. I also promised that I'm not going to stop on that. So I won't!

Today, I modernised my #NodeJs samples. If you're looking for how to start your journey with #EventSourcing, then start with my repo: https://github.com/oskardudycz/EventSourcing.NodeJS

Now it uses the latest #NodeJs, #EventStoreDB, etc!

We should carefully draw boundaries between our events. And we should also care about data privacy.

In the, I explained techniques specific to event-driven systems and tools like #Kafka, #Marten, and #EventStoreDB. But I also put them into a wider context.

After this article, I hope you see that applying privacy regulations to event-driven systems differs mainly from the technical patterns in handling them.

2/

#EventSourcing in #Java?

Full sample with #SpringBoot?

Why not!

I just upgraded my Java samples to #SpringBoot 3 and #EventStoreDB 4: https://github.com/oskardudycz/EventSourcing.JVM/pull/38.

If you're looking for a place where:
- you could learn #EventSourcing from scratch with the self-paced kit,
- you can learn how to handle distributed processes, uniqueness, versioning,
- see real-world samples orchestrating that together.

Then I think my repo is a decent place to start your journey!

To close this, we‘re using subscriptions from #eventstoredb with stored checkpoints (thx @oskardudycz for showing me), each achievement has their own subscription. The consumed events (finished cards) trigger the checks (if achievements have been reached). This enables to introduce new achievements that are granted to players in retrospective.

💛 #eventsourcing

5/5

I just applied #OpenTelemetry to my #EventSourcing in #dotnet samples: https://github.com/oskardudycz/EventSourcing.NetCore/pull/181.

It needs enhancements (especially around events, error handling, tagging etc.) but basic flow together with propagation is working fine for #Marten, #Kafka and #EventStoreDB.

Check it up! Feedback is more than welcome 😊