This blog is for us to share our experiences and insights. Here we will highlight various topics related to web development with PHP, be it design patterns, testing or DevOps. The focus will be on topics related to domain-driven design and event sourcing.
Version 1.3.0 of the patchlevel/event-sourcing-phpstan-extension adds three new rules that guard the state of your aggregates: they report properties that no event ever fills, state that nothing reads, and writes that happen outside an apply method. Every rule can now be turned off individually.
In part one we designed our events. But what if you got it wrong, or the business simply changed its mind? Events are immutable and your history lives forever, so you cannot just edit them. This second part walks through a toolbox of techniques, from a simple rename to rebuilding the whole store, so you can evolve your events without ever breaking your history.
One of the first things that trips up newcomers to event sourcing is figuring out how to cut their events. Should it be one big event or many small ones? There is no universal answer, it depends on your domain and on how much the decision you are recording actually changes. In this first part of a two-part series we model the same information in two very different ways and work out when each one is the right call.
Version 3.20.0 of patchlevel/event-sourcing focuses on operating event-sourced systems over the long run. You can now keep reading old messages whose header classes were removed, and you can skip the confirmation prompts of the CLI commands to use them in automation.
A lot has happened since our last release post: eight minor releases for patchlevel/event-sourcing. We added an instant retry command bus, subscription cleanup, auto initialized aggregates, PHP 8.5 and Symfony 8 support and much more. Time to catch up on all the highlights from 3.12 to 3.19.
Discover what is new in patchlevel/event-sourcing 3.11.0, including improved console commands, a powerful query bus, and gap detection for subscriptions. This release focuses on enhancing developer experience and system resilience with practical, real-world features.
We are excited to announce the release of patchlevel/event-sourcing version 3.9.0 and 3.10.0! These updates introduces features around error handling for the subscription engine and also some nice DX features and PHP 8.4 support.
We are excited to announce the release of patchlevel/event-sourcing version 3.8.0! This update introduces features such as lookup, command bus, read-only event store, and the official release of the stream store. In this post, we will walk you through the key changes.
This article addresses the common concern regarding the performance of event sourcing, particularly the speed at which long-living aggregates with many events are loaded. It explores solutions such as snapshotting and stream splitting to optimize aggregate loading. Furthermore, projections allow for the creation of highly flexible and optimized read models, each can be tailored to specific needs.
We’re excited to announce the release of our php library patchlevel/event-sourcing version 3.7.0. This release features better testing capabilities with InMemorySubscriptionStore::clear, improved subscription performance and a new #[Stream] attribute for micro aggregates!
We are happy to announce the release of the php event sourcing library in version 3.6.0. This release contains several exciting new features like Pipe and Reducer. In this blog post, we will provide you with an overview of the changes.
Today we want to show you how to use the event sourcing library with Symfony. We will guide you through the installation, show you how to use the bundle in a small example and give you a working hotel REST-API.
This post explores techniques for handling data removal in event-sourced applications, focusing on compliance and privacy needs, like GDPR. By using methods such as Crypto Shredding and Tokenization for anticipated data deletions, and History Rewriting for unexpected cases, developers can securely remove data while maintaining an immutable event store.
We are happy to announce the release of the php event sourcing library in version 3.5.0. This release contains several exciting new features and improvements. In this blog post, we will provide you with an overview of the changes.
Today, our topic will be the benefits of event sourcing. We will discuss the possibilities it offers without data loss. The main topics will be reporting & analytics, software architecture & scalability, testing and auditing.
The event bus is a powerful design pattern in the world of event sourcing. It allows you to decouple the event producers from the event consumers. But it also has its downsides.
Often, when talking with people about event sourcing and whether they have used it, I get the same answer: "No, I have never used it, but I want to!" My question afterward is always: "So why the hesitation?" Let’s take a look at that.
We are happy to announce the release of the php event sourcing library in version 3.4.0. This release contains several exciting new features and improvements. In this blog post, we will provide you with an overview of the changes.
Inspired by a question on GitHub regarding the combined usage of ORM entities with event sourcing aggregates I decided to write how to do exactly that.