event-sourcing icon indicating copy to clipboard operation
event-sourcing copied to clipboard

An event sourcing library, complete with all the essential features, powered by the reliable Doctrine ecosystem and focused on developer experience.

Results 63 event-sourcing issues
Sort by recently updated
recently updated
newest added

I think we can "archive" old versions in docs. By that I mean versions that we no longer support, we could delete them and redirect to the next newest version....

documentation

* We use semver * Which versions do we support? * What does experimental mean * What does internal mean

documentation

Hi, Given I use event sourcing for a online shop with a Product aggregate. A product has events like: `ProductCreated` (playhead 1) → `ProductTitleChanged` (playhead 2) → `ProductPriceChanged` (playhead 3)...

For this we need these points solved: - [x] Migrate from annotation like `@covers` to attributes `#[CoversClass]` etc. Done in https://github.com/patchlevel/event-sourcing/pull/732 - [ ] Drop PHP 8.2 support - [x]...

enhancement

We sometimes have Aggregates that do not have an explicit `create` event, they just come into existence by whatever event is recorded first (often this is some ID managed outside...

We already talked once about this and I still think this trait should be removed but the neat functionality should stay. Right now my projections are looking like this: ```php...

RFC
version: 4.0.x

We should use `jsonb` when the user is using postgresql. This give the user better query capabilities on the json fields in the store. When this PR is released https://github.com/doctrine/dbal/pull/6693...