pawelkaczor/akka-ddd
This is a Scala-based framework for building distributed, event-sourced applications using the Akka actor model. It provides core abstractions for managing stateful actors, including aggregate roots, sagas, and process managers, while handling cluster sharding and reliable message delivery. The system also supports HTTP command routing, SQL-based view updates, and scheduled task execution, all backed by an EventStore persistence layer.
55.3
Adequate · 4 August 2026
3.6k
lines of production code
Scala
primary language
1
bus factor · 5 authors in all
3
measurements over time
How it got here
2014 · DDD framework refactoring and feature expansion
The project underwent a significant architectural overhaul, migrating to a multi-module build structure and modernizing its dependency management. Core Domain-Driven Design components, such as Aggregate Roots and Sagas, were refactored to improve separation of concerns, observability, and cluster sharding support. New features were introduced for process management, event sourcing, and reliable message delivery, while legacy test utilities and abstractions were removed.
15 changes
2015 · Event-driven architecture and scheduling infrastructure
This period focused on implementing core event-driven capabilities, including a new view-update module for SQL-based state management and a scheduling system for deadline tracking. The work also introduced HTTP command handling and message deduplication to support reliable message processing. Comprehensive test coverage was added for these new components to ensure correctness.
13 changes
2016–2018 · Protocol and monitoring expansion
This period focused on expanding the Akka DDD framework with new protocol modules, monitoring capabilities, and message metadata support. The work included refactoring aggregate protocols, introducing event tagging for persistence, and adding comprehensive test coverage for domain models and core components.
13 changes
Survey your own repository
pawelkaczor/akka-ddd 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 5c7adf45d2 — 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.