home.social

#eventsourcing — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #eventsourcing, aggregated by home.social.

  1. RE: floss.social/@monospace/116923

    We (should) do this for configuration, why not for the application data, too? #EventSourcing

  2. RE: floss.social/@monospace/116923

    We (should) do this for configuration, why not for the application data, too? #EventSourcing

  3. RE: floss.social/@monospace/116923

    We (should) do this for configuration, why not for the application data, too? #EventSourcing

  4. RE: floss.social/@monospace/116923

    We (should) do this for configuration, why not for the application data, too? #EventSourcing

  5. RE: floss.social/@monospace/116923

    We (should) do this for configuration, why not for the application data, too? #EventSourcing

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

    planetgeek.ch/2026/07/14/event

    After this post, there will be a summer break.

    #EventSourcing #fsharp

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

    planetgeek.ch/2026/07/14/event

    After this post, there will be a summer break.

    #EventSourcing #fsharp

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

    planetgeek.ch/2026/07/14/event

    After this post, there will be a summer break.

    #EventSourcing #fsharp

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

    planetgeek.ch/2026/07/14/event

    After this post, there will be a summer break.

    #EventSourcing #fsharp

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

    planetgeek.ch/2026/07/14/event

    After this post, there will be a summer break.

    #EventSourcing #fsharp

  11. 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: patchlevel.dev/blog/cutting-yo

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

  12. 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: patchlevel.dev/blog/cutting-yo

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

  13. 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: patchlevel.dev/blog/cutting-yo

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

  14. 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: patchlevel.dev/blog/cutting-yo

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

  15. 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: patchlevel.dev/blog/cutting-yo

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

  16. Back to bi-temporal events in part 12 of my event sourcing blog post series: planetgeek.ch/2026/07/07/event

    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

  17. Back to bi-temporal events in part 12 of my event sourcing blog post series: planetgeek.ch/2026/07/07/event

    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

  18. Back to bi-temporal events in part 12 of my event sourcing blog post series: planetgeek.ch/2026/07/07/event

    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

  19. Back to bi-temporal events in part 12 of my event sourcing blog post series: planetgeek.ch/2026/07/07/event

    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

  20. Back to bi-temporal events in part 12 of my event sourcing blog post series: planetgeek.ch/2026/07/07/event

    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

  21. 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!

    patchlevel.dev/blog/what-is-ne

    #TechBlog #PHP #DDD #EventSourcing

  22. 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!

    patchlevel.dev/blog/what-is-ne

    #TechBlog #PHP #DDD #EventSourcing

  23. 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!

    patchlevel.dev/blog/what-is-ne

    #TechBlog #PHP #DDD #EventSourcing

  24. 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: patchlevel.dev

    #PHP #EventSourcing #OpenSource

  25. 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: patchlevel.dev

    #PHP #EventSourcing #OpenSource

  26. 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: patchlevel.dev

    #PHP #EventSourcing #OpenSource

  27. 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: patchlevel.dev

    #PHP #EventSourcing #OpenSource

  28. 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: patchlevel.dev

    #PHP #EventSourcing #OpenSource

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

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

    #EventSourcing

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

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

    #EventSourcing

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

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

    #EventSourcing

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

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

    #EventSourcing

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

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

    #EventSourcing

  34. 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.”

  35. 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.”

  36. 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.”

  37. 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.”

  38. 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.”

  39. 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:

    planetgeek.ch/2026/06/23/event

    #EventSourcing #dotnet #fsharp

  40. 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:

    planetgeek.ch/2026/06/23/event

    #EventSourcing #dotnet #fsharp