#eventsourcing — Public Fediverse posts

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):

https://www.planetgeek.ch/2026/07/14/event-sourcing-undo-set-remove-based-bi-temporal-events-because-we-must/

After this post, there will be a summer break.

#EventSourcing #fsharp

In part 13 of my event sourcing series, we take a look at how to undo bi-temporal events (why and how):

https://www.planetgeek.ch/2026/07/14/event-sourcing-undo-set-remove-based-bi-temporal-events-because-we-must/

After this post, there will be a summer break.

#EventSourcing #fsharp

In part 13 of my event sourcing series, we take a look at how to undo bi-temporal events (why and how):

https://www.planetgeek.ch/2026/07/14/event-sourcing-undo-set-remove-based-bi-temporal-events-because-we-must/

After this post, there will be a summer break.

#EventSourcing #fsharp

In part 13 of my event sourcing series, we take a look at how to undo bi-temporal events (why and how):

https://www.planetgeek.ch/2026/07/14/event-sourcing-undo-set-remove-based-bi-temporal-events-because-we-must/

After this post, there will be a summer break.

#EventSourcing #fsharp

In part 13 of my event sourcing series, we take a look at how to undo bi-temporal events (why and how):

https://www.planetgeek.ch/2026/07/14/event-sourcing-undo-set-remove-based-bi-temporal-events-because-we-must/

After this post, there will be a summer break.

#EventSourcing #fsharp

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.

#EventSourcing #dotnet #fsharp

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.

#EventSourcing #dotnet #fsharp

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.

#EventSourcing #dotnet #fsharp

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.

#EventSourcing #dotnet #fsharp

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.

#EventSourcing #dotnet #fsharp

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

#TechBlog #PHP #DDD #EventSourcing

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

#TechBlog #PHP #DDD #EventSourcing

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

#TechBlog #PHP #DDD #EventSourcing

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

#PHP #EventSourcing #OpenSource

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

#PHP #EventSourcing #OpenSource

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

#PHP #EventSourcing #OpenSource

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

#PHP #EventSourcing #OpenSource

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

#PHP #EventSourcing #OpenSource

This is coming up soon! Join me on Monday for my Ted Talk at OpenValue in Munich:
https://www.meetup.com/openvaluemuenchen/events/315218662

And you can check out my event-sourced travel app at http://jittertravel.com/calendar

#EventSourcing

This is coming up soon! Join me on Monday for my Ted Talk at OpenValue in Munich:
https://www.meetup.com/openvaluemuenchen/events/315218662

And you can check out my event-sourced travel app at http://jittertravel.com/calendar

#EventSourcing

This is coming up soon! Join me on Monday for my Ted Talk at OpenValue in Munich:
https://www.meetup.com/openvaluemuenchen/events/315218662

And you can check out my event-sourced travel app at http://jittertravel.com/calendar

#EventSourcing

This is coming up soon! Join me on Monday for my Ted Talk at OpenValue in Munich:
https://www.meetup.com/openvaluemuenchen/events/315218662

And you can check out my event-sourced travel app at http://jittertravel.com/calendar

#EventSourcing

This is coming up soon! Join me on Monday for my Ted Talk at OpenValue in Munich:
https://www.meetup.com/openvaluemuenchen/events/315218662

And you can check out my event-sourced travel app at http://jittertravel.com/calendar

#EventSourcing

My answer to a lot of questions I get about #EventSourcing seems to be “well, what do you do now?” And then I add, “with event-sourcing, it’s probably easier to fix/recover/adapt/etc.”

My answer to a lot of questions I get about #EventSourcing seems to be “well, what do you do now?” And then I add, “with event-sourcing, it’s probably easier to fix/recover/adapt/etc.”

My answer to a lot of questions I get about #EventSourcing seems to be “well, what do you do now?” And then I add, “with event-sourcing, it’s probably easier to fix/recover/adapt/etc.”

My answer to a lot of questions I get about #EventSourcing seems to be “well, what do you do now?” And then I add, “with event-sourcing, it’s probably easier to fix/recover/adapt/etc.”

My answer to a lot of questions I get about #EventSourcing seems to be “well, what do you do now?” And then I add, “with event-sourcing, it’s probably easier to fix/recover/adapt/etc.”

We released 3.19.2 of event-sourcing! See here for the changelog: https://github.com/patchlevel/event-sourcing/releases/tag/3.19.2
#PHP #DDD #EventSourcing

We released 3.19.2 of event-sourcing! See here for the changelog: https://github.com/patchlevel/event-sourcing/releases/tag/3.19.2
#PHP #DDD #EventSourcing

We released 3.19.2 of event-sourcing! See here for the changelog: https://github.com/patchlevel/event-sourcing/releases/tag/3.19.2
#PHP #DDD #EventSourcing

We released 3.19.2 of event-sourcing! See here for the changelog: https://github.com/patchlevel/event-sourcing/releases/tag/3.19.2
#PHP #DDD #EventSourcing

We released 3.19.2 of event-sourcing! See here for the changelog: https://github.com/patchlevel/event-sourcing/releases/tag/3.19.2
#PHP #DDD #EventSourcing

In part 11 of my event sourcing series, I discuss consistency and why we don't use aggregates or dynamic consistency boundaries to solve it:

https://www.planetgeek.ch/2026/06/23/event-sourcing-aggregates-dynamic-consistency-boundaries-or-what/

#EventSourcing #dotnet #fsharp

In part 11 of my event sourcing series, I discuss consistency and why we don't use aggregates or dynamic consistency boundaries to solve it:

https://www.planetgeek.ch/2026/06/23/event-sourcing-aggregates-dynamic-consistency-boundaries-or-what/

#EventSourcing #dotnet #fsharp