Elektrine
Log in Register

#eventsourcing

9 posts · Last used 10d

Back to Timeline
danielbadura
Daniel Badura @danielbadura@phpc.social · Aug 05, 2026
I wrote a small blog post about the new release of patchlevel/event-sourcing-phpstan-extension, 1.3.0 adds three new rules. They report aggregate properties that no event ever fills, state that nothing ever reads, and state that changes outside an apply method. Also, every rule can be turned off individually. Feel free to check it out! https://patchlevel.dev/blog/what-is-new-in-the-event-sourcing-phpstan-extension-1-3-0 #TechBlog #PHP #DDD #EventSourcing #PHPStan #StaticAnalysis
0
0
0
dgafka
Dariusz Gafka @dgafka@phpc.social · Jul 25, 2026
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
0
0
0
danielbadura
Daniel Badura @danielbadura@phpc.social · Jul 22, 2026
Requirements change, but your events are immutable and your history lives forever. So how do you evolve them without breaking anything? I just published the second and final part of my two-part series on event design: "Evolving Your Events Over Time." It walks through the whole toolbox of event evolution, from a free rename to rebuilding the whole store. Feel free to check it out! https://patchlevel.dev/blog/evolving-your-events-over-time #TechBlog #PHP #DDD #EventSourcing #EventDesign
4
0
3
patchlevel
patchlevel @patchlevel@phpc.social · Jul 20, 2026
We released 1.3.0 of event-sourcing-phpstan-extension! See here for the changelog: https://github.com/patchlevel/event-sourcing-phpstan-extension/releases/tag/1.3.0 #PHP #DDD #EventSourcing #PHPStan #StaticAnalysis
0
0
0
reiver
@reiver ⊼ (Charles) :batman: @reiver@mastodon.social · May 03, 2026
There is a comparison that can be made between ActivityPub and Event-Sourcing. 1/ With Event-Sourcing, your source-of-truth is an append-only series of events. Ex: USER_REGISTERED, EMAIL_ADDRESS_VERIFIED, PASSWORD_CHANGED, etc. In ActivityPub, this is similar to the inbox, outbox, etc being an append-only series of Activity. Ex: Create, Like, Undo, etc. ... #ActivityPub #ActivityStreams #EventSourcing #FediDev
4
3
7
reiver
@reiver ⊼ (Charles) :batman: @reiver@mastodon.social · May 03, 2026
Replying to @reiver@mastodon.social
There is a comparison that can be made between ActivityPub and Event-Sourcing. 2/ With Event-Sourcing, you can "project" the events to get another (often more peformant) view of the data in the events. Without having to incur the cost of having to read all the events to figure out the final state. ... #ActivityPub #ActivityStreams #EventSourcing #FediDev
1
1
4
reiver
@reiver ⊼ (Charles) :batman: @reiver@mastodon.social · May 03, 2026
Replying to @reiver@mastodon.social
There is a comparison that can be made between ActivityPub and Event-Sourcing. 3/ With ActivityPub, Activities are often applied to an object. That object gets assigned an ID in the form of a URL. (And, by URL I mean URL, URI, IRI, etc.) One doesn't have to read through all the Activities in an inbox, outbox, etc to get the final state of an object. One can just get the JSON-LD document from the object's ID URL to get the final state. #ActivityPub #ActivityStreams #EventSourcing #FediDev
1
2
4

You've seen all posts