#eventsourcing — Public Fediverse posts

CQRS, async with retries and dead-lettering, event sourcing, projections, workflows. That feature list usually means a platform team.

I built it as an e-commerce shop on Tempest + Ecotone. The entire messaging layer: about a dozen small classes of business logic. No worker command, no repository, no queue wiring.

The Order aggregate IS the Tempest database model. One class, both frameworks.

https://github.com/ecotoneframework/tempest-ecotone-demo

#PHP #CQRS #EventSourcing

We just published *Cutting Your Events the Right Way*, the first part of a two-part series on event design.

It takes the same customer data, models it as one big event and as several small ones, and works out when each cut is the right call.

Read it here: https://patchlevel.dev/blog/cutting-your-events-the-right-way

#EventSourcing #DDD #PHP #SoftwareArchitecture #EventDriven #TechBlog

New blog post: My Work in Progress Ruby stack ismaelcelis.com/posts/2026-0... #eventsourcing #cqrs

My WIP Ruby stack

I have been iterating on Event Sourcing and CQRS architectures for nearly a decade. When I first started with this pattern around 2016 and 2017, the implementation was considerably more complex. Over the years I have stripped it back again and again, and what I have arrived at now is something I'm genuinely happy with: a small, focused TypeScript library backed by DynamoDB that does exactly what it needs to and nothing more: https://coderbyheart.com/es-and-cqrs-on-aws-simplified #eventsourcing #cqrs #aws

Your customer received €50. The notification on their phone says "New balance: €100." Should be €150 — the notification queried the read model before the projection committed.

That race lives in most CQRS systems. Wrote up how to close it for good in PHP — by emitting derived events from inside the projection.

https://blog.ecotone.tech/stop-subscribing-to-domain-events

#PHP #EventSourcing #CQRS #Ecotone

Next week I will speak at BASTA! Conference in Frankfurt, about #SoftwareArchitecture, #CSharp, #LLM use in #CQRS and #EventSourcing systems, and much else. 🌎 Bring your thinking hat for my #BASTAllionaire game show 🎉! Say hello if you see me, or come talk about #DevExpress. 🚀 https://basta.net/frankfurt/

I've developed #Ecotone Framework based on the principle that we should fully focus on business features, not the technical infrastructure part.

However, in some cases where optimization of requests is critical, auto-initialization may come with a performance penalty.

For this #Ecotone provides now migrations, that can help optimize this process:

https://docs.ecotone.tech/modelling/migrations-storage

#PHP #Messaging #CQRS #EventSourcing #DDD #SoftwareArchitecture

I broke down Event Sourcing in Quarkus using Java records, sealed types, pure functions, and a clean CQRS split.

Fully hands-on. No magic. Just data, folds, and clear architecture.
If you want to understand event sourcing without the hype, this one is for you.

👉 https://www.the-main-thread.com/p/event-sourcing-quarkus-java-records-cqrs-tutorial

#Java #Quarkus #EventSourcing #CQRS #DataOrientedDesign

https://zalas.pl/object-oriented-event-sourcing/

#ddd #dddesign #eventsourcing #kotlin

https://zalas.pl/deriving-state-from-events/

#ddd #dddesign #eventsourcing #kotlin

https://zalas.pl/functional-event-sourcing-example-in-kotlin/

#ddd #dddesign #eventsourcing #kotlin

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 🙂