SwissBorg/akka-persistence-postgres
This system is a PostgreSQL-specific implementation of the Akka Persistence plugin, designed to store and retrieve persistent state for distributed actors. It manages write and read operations through configurable journal partitioning, metadata tracking, and tag-based querying, while also handling snapshot storage. The system includes migration tools to upgrade existing JDBC-based schemas to the new PostgreSQL structure.
51.8
Adequate · 4 August 2026
3.5k
lines of production code
Scala
primary language
3
bus factor · 59 authors in all
3
measurements over time
How it got here
2014–2016 · Project restructuring and build standardization
The period focused on refactoring the project into a multi-module structure and standardizing the build configuration. Hardcoded database configurations and obsolete test suites were removed to support a more flexible, multi-backend approach, while new scripts and build plugins were added to streamline development and release workflows.
9 changes
2019–2023 · PostgreSQL persistence implementation
This period focused on replacing the generic JDBC persistence layer with a dedicated PostgreSQL implementation using Slick. The work introduced support for partitioned journal tables, metadata tracking, and asynchronous serialization to improve performance and scalability. Comprehensive test coverage and migration scripts were added to support the new architecture.
26 changes
Survey your own repository
SwissBorg/akka-persistence-postgres 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 4 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 45b809cb3e — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.