spatie/laravel-event-projector — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2019-09-20
Add a full audit trail to a Laravel app so every data change is recorded and replayable
Build a financial or order-management system where understanding history matters as much as current state
Maintain a fast, current-state table (like a shopping cart) automatically generated from a stream of events
Fix a past bug retroactively by replaying stored events with corrected logic
| spatie/laravel-event-projector | david-crty/databasement | gargron/fileupload | |
|---|---|---|---|
| Stars | 637 | 815 | 456 |
| Language | PHP | PHP | PHP |
| Last pushed | 2019-09-20 | — | 2022-03-03 |
| Maintenance | Dormant | — | Dormant |
| Setup difficulty | moderate | easy | moderate |
| Complexity | 3/5 | 2/5 | 2/5 |
| Audience | developer | ops devops | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires an existing Laravel application and a shift in how data writes are structured around events.
A Laravel library for event sourcing, instead of saving just the current state of your data, it records every change as an event and builds fast, readable projections from that full history.
Mainly PHP. The stack also includes PHP, Laravel.
Dormant — no commits in 2+ years (last push 2019-09-20).
License terms are not described in the explanation, check the repository directly before use.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.