pyeventsourcing/eventsourcing
This system is an event sourcing library for Python that provides infrastructure for building domain-driven applications. It supports multiple aggregate modeling styles, including standard, Pydantic, and msgspec-based models, with features like automatic snapshotting, compression, and encryption. The library also introduces a Domain Command Bus (DCB) framework for managing bounded contexts and consistency boundaries. It includes comprehensive tooling for development, testing, and benchmarking, alongside a suite of example applications demonstrating various architectural patterns like vertical slices and full-text search projections.
56.8
Adequate · 31 July 2026
15k
lines of production code
Python
primary language
1
bus factor · 31 authors in all
4
measurements over time
How it got here
2015–2024 · Infrastructure modernization and test expansion
The project underwent a comprehensive overhaul of its development infrastructure, introducing a Makefile, Docker-based local environment, and automated release scripts to standardize the developer experience. Concurrently, the codebase was restructured into modular components, and the test suite was significantly expanded to cover application, domain, and persistence layers. This period also saw the addition of numerous example applications demonstrating advanced features like metadata handling, snapshotting, and time-travel queries.
20 changes
2025 · DCB and example expansion
This period focused on introducing the Domain Command Bus (DCB) framework and expanding the library's example suite. New examples demonstrated DCB patterns, full-text search capabilities, and vertical slice architectures across various backends.
17 changes
Survey your own repository
pyeventsourcing/eventsourcing was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 31 July 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 099c92ddcb — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.