Adding Event Sourcing to an existing PHP project (for the right reasons)
summary
Adds event sourcing onto an existing PHP codebase to solve reporting historization, using MongoDB (ext-mongodb), RabbitMQ buffering and Symfony tooling, proving it at scale: 3 million events stored, projectors able to rebuild from scratch in ~5 minutes, runner run as short bursts via cron (stop after ~14m) to avoid PHP long‑process issues, idempotent executors with projection state TTLs, produced reliable reports and an open‑source Symfony bundle for the stack.
AI-written summary · about
chapters (4)
related talks
41mAdding Event Sourcing to an existing PHP project (for the right reasons)
25mCQRS and Event Sourcing: May the Event Be with You
58mPHP + ES + CQRS + DDD = ? An integrated strategy
32mEvent Sourcing in Laravel with EventSauce
32mEvent Sourcing in Laravel
40mEvent Sourcing with Laravel
02h 53mPractical design patterns in PHP (Part 3)
34mWhy PHP and Symfony are still in the game