#eventsourcing — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #eventsourcing, aggregated by home.social.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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!
-
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!
-
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!
-
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!
-
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!
-
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 -
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 -
We released 3.17.1 of event-sourcing-bundle! See here for the changelog: https://github.com/patchlevel/event-sourcing-bundle/releases/tag/3.17.1
#PHP #DDD #EventSourcing #Symfony -
We released 3.17.1 of event-sourcing-bundle! See here for the changelog: https://github.com/patchlevel/event-sourcing-bundle/releases/tag/3.17.1
#PHP #DDD #EventSourcing #Symfony -
We released 3.17.1 of event-sourcing-bundle! See here for the changelog: https://github.com/patchlevel/event-sourcing-bundle/releases/tag/3.17.1
#PHP #DDD #EventSourcing #Symfony -
We released 3.17.1 of event-sourcing-bundle! See here for the changelog: https://github.com/patchlevel/event-sourcing-bundle/releases/tag/3.17.1
#PHP #DDD #EventSourcing #Symfony -
We released 3.17.1 of event-sourcing-bundle! See here for the changelog: https://github.com/patchlevel/event-sourcing-bundle/releases/tag/3.17.1
#PHP #DDD #EventSourcing #Symfony -
RE: https://floss.social/@monospace/116923591603748773
We (should) do this for configuration, why not for the application data, too? #EventSourcing
-
RE: https://floss.social/@monospace/116923591603748773
We (should) do this for configuration, why not for the application data, too? #EventSourcing
-
RE: https://floss.social/@monospace/116923591603748773
We (should) do this for configuration, why not for the application data, too? #EventSourcing
-
RE: https://floss.social/@monospace/116923591603748773
We (should) do this for configuration, why not for the application data, too? #EventSourcing
-
RE: https://floss.social/@monospace/116923591603748773
We (should) do this for configuration, why not for the application data, too? #EventSourcing
-
In part 13 of my event sourcing series, we take a look at how to undo bi-temporal events (why and how):
After this post, there will be a summer break.
-
In part 13 of my event sourcing series, we take a look at how to undo bi-temporal events (why and how):
After this post, there will be a summer break.
-
In part 13 of my event sourcing series, we take a look at how to undo bi-temporal events (why and how):
After this post, there will be a summer break.
-
In part 13 of my event sourcing series, we take a look at how to undo bi-temporal events (why and how):
After this post, there will be a summer break.
-
In part 13 of my event sourcing series, we take a look at how to undo bi-temporal events (why and how):
After this post, there will be a summer break.
-
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
-
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
-
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
-
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
-
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
-
Back to bi-temporal events in part 12 of my event sourcing blog post series: https://www.planetgeek.ch/2026/07/07/event-sourcing-set-and-remove-based-bi-temporal-events/
This time, we look at set-and-remove-based bi-temporal events - the second variant of bi-temporal events in our system. You'll see why they are needed, and what additional problems this kind of event brings to the table.
-
Back to bi-temporal events in part 12 of my event sourcing blog post series: https://www.planetgeek.ch/2026/07/07/event-sourcing-set-and-remove-based-bi-temporal-events/
This time, we look at set-and-remove-based bi-temporal events - the second variant of bi-temporal events in our system. You'll see why they are needed, and what additional problems this kind of event brings to the table.
-
Back to bi-temporal events in part 12 of my event sourcing blog post series: https://www.planetgeek.ch/2026/07/07/event-sourcing-set-and-remove-based-bi-temporal-events/
This time, we look at set-and-remove-based bi-temporal events - the second variant of bi-temporal events in our system. You'll see why they are needed, and what additional problems this kind of event brings to the table.
-
Back to bi-temporal events in part 12 of my event sourcing blog post series: https://www.planetgeek.ch/2026/07/07/event-sourcing-set-and-remove-based-bi-temporal-events/
This time, we look at set-and-remove-based bi-temporal events - the second variant of bi-temporal events in our system. You'll see why they are needed, and what additional problems this kind of event brings to the table.
-
Back to bi-temporal events in part 12 of my event sourcing blog post series: https://www.planetgeek.ch/2026/07/07/event-sourcing-set-and-remove-based-bi-temporal-events/
This time, we look at set-and-remove-based bi-temporal events - the second variant of bi-temporal events in our system. You'll see why they are needed, and what additional problems this kind of event brings to the table.
-
Version 3.20.0 of patchlevel/event-sourcing is out! You can now keep reading old messages whose header classes were removed, and the destructive CLI commands accept a `--force` flag so you can run them from scripts and pipelines.
I wrote a blog post about the release, feel free to check it out!
https://patchlevel.dev/blog/what-is-new-in-php-event-sourcing-3-20
-
Version 3.20.0 of patchlevel/event-sourcing is out! You can now keep reading old messages whose header classes were removed, and the destructive CLI commands accept a
--force flag so you can run them from scripts and pipelines.I wrote a blog post about the release, feel free to check it out!
https://patchlevel.dev/blog/what-is-new-in-php-event-sourcing-3-20
-
Version 3.20.0 of patchlevel/event-sourcing is out! You can now keep reading old messages whose header classes were removed, and the destructive CLI commands accept a `--force` flag so you can run them from scripts and pipelines.
I wrote a blog post about the release, feel free to check it out!
https://patchlevel.dev/blog/what-is-new-in-php-event-sourcing-3-20
-
We launched patchlevel.dev a couple of weeks ago! Our open source PHP event-sourcing ecosystem was scattered across
separate MkDocs sites, a blog on our consultancy site, and GitHub READMEs.Now everything lives in one place: the event-sourcing library, the Symfony and Laravel integrations, and all supporting
libraries side by side. Plus unified search across docs and blog, and docs that stay in sync with every release.Have a look: https://patchlevel.dev
-
We launched patchlevel.dev a couple of weeks ago! Our open source PHP event-sourcing ecosystem was scattered across
separate MkDocs sites, a blog on our consultancy site, and GitHub READMEs.Now everything lives in one place: the event-sourcing library, the Symfony and Laravel integrations, and all supporting
libraries side by side. Plus unified search across docs and blog, and docs that stay in sync with every release.Have a look: https://patchlevel.dev
-
We launched patchlevel.dev a couple of weeks ago! Our open source PHP event-sourcing ecosystem was scattered across
separate MkDocs sites, a blog on our consultancy site, and GitHub READMEs.Now everything lives in one place: the event-sourcing library, the Symfony and Laravel integrations, and all supporting
libraries side by side. Plus unified search across docs and blog, and docs that stay in sync with every release.Have a look: https://patchlevel.dev
-
We launched patchlevel.dev a couple of weeks ago! Our open source PHP event-sourcing ecosystem was scattered across
separate MkDocs sites, a blog on our consultancy site, and GitHub READMEs.Now everything lives in one place: the event-sourcing library, the Symfony and Laravel integrations, and all supporting
libraries side by side. Plus unified search across docs and blog, and docs that stay in sync with every release.Have a look: https://patchlevel.dev
-
We launched patchlevel.dev a couple of weeks ago! Our open source PHP event-sourcing ecosystem was scattered across
separate MkDocs sites, a blog on our consultancy site, and GitHub READMEs.Now everything lives in one place: the event-sourcing library, the Symfony and Laravel integrations, and all supporting
libraries side by side. Plus unified search across docs and blog, and docs that stay in sync with every release.Have a look: https://patchlevel.dev
-
This is coming up soon! Join me on Monday for my Ted Talk at OpenValue in Munich:
https://www.meetup.com/openvaluemuenchen/events/315218662And you can check out my event-sourced travel app at http://jittertravel.com/calendar
-
This is coming up soon! Join me on Monday for my Ted Talk at OpenValue in Munich:
https://www.meetup.com/openvaluemuenchen/events/315218662And you can check out my event-sourced travel app at http://jittertravel.com/calendar
-
This is coming up soon! Join me on Monday for my Ted Talk at OpenValue in Munich:
https://www.meetup.com/openvaluemuenchen/events/315218662And you can check out my event-sourced travel app at http://jittertravel.com/calendar
-
This is coming up soon! Join me on Monday for my Ted Talk at OpenValue in Munich:
https://www.meetup.com/openvaluemuenchen/events/315218662And you can check out my event-sourced travel app at http://jittertravel.com/calendar
-
This is coming up soon! Join me on Monday for my Ted Talk at OpenValue in Munich:
https://www.meetup.com/openvaluemuenchen/events/315218662And you can check out my event-sourced travel app at http://jittertravel.com/calendar