Ecotone
Stop Subscribing to Domain Events
The notification fires before the projection commits. The user sees a stale balance. Emitting derived events from inside the projection — as the read model — closes the race for good.
PHP
When One Worker Can't Keep Up: Scaling Projections
Scale event sourcing projections with partitioned processing, track-based gap detection, and streaming. Learn how Ecotone handles concurrent transactions.
PHP
Your Projections Will Fail — Make Them Resilient
Decouple projections from command handlers with async execution. Learn self-healing, failure isolation, batching, and polling in Ecotone's ProjectionV2.
PHP
Why Projections Exist — Your First Read Model
Learn why Event Sourcing needs projections and build your first read model with Ecotone's ProjectionV2. Lifecycle hooks, state, and CLI included.
PHP
Make Your PHP Domain Speak the Business Language
Your PHP domain code should read like the business problem it solves — not like a framework manual. PHP attributes, plain classes, and a domain a new hire can understand in 30 seconds.
PHP
Starting with Event Sourcing in PHP
How to build event-sourced aggregates and projections in PHP with Ecotone — native event store, snapshots, projections, replay, and tested in-memory.
PHP
Async PHP Done Right — Per-Handler Channels
Why one attribute on a method beats hand-rolled queue workers in PHP. Per-handler channels, transactional outbox + RabbitMQ, and the same code on Symfony or Laravel.
PHP
Event Handling in PHP — From Tangled Code to Clean Flows
Stop cramming side effects into one PHP service. Use domain events with EventBus and per-handler isolation to split main flows from sub-flows — works on Symfony, Laravel, and standalone.
PHP
CQRS in PHP — Stop Mixing Reads and Writes
Why your PHP read methods are silently writing data — and how Command/Query separation with EventBus, CommandBus, and QueryBus fixes it. Examples for Symfony, Laravel, and standalone.
PHP
Enterprise PHP in 2026: The Patterns You're Missing
How modern PHP teams ship reliable, distributed systems in 2026 — outbox, sagas, event sourcing, and per-handler resiliency without rewriting Symfony or Laravel.