holunda-io/camunda-bpm-taskpool
This system is a distributed task and data management platform that synchronizes state between a Camunda BPM engine and a persistent view layer. It captures process and task events from the engine, processes them through an event-sourcing core, and propagates updates to both relational (JPA) and document (MongoDB) storage backends. The architecture supports flexible transactional sending of commands and provides comprehensive query APIs for retrieving tasks, data entries, and process instances.
54.9
Adequate · 29 July 2026
18k
lines of production code
Kotlin
primary language
2
bus factor · 41 authors in all
3
measurements over time
How it got here
2018–2021 · Polyflow view and taskpool API expansion
This period focused on expanding the Polyflow framework with comprehensive query and filtering APIs for tasks, data entries, and process variables. It introduced new persistence layers for the view layer, including MongoDB, JPA, and in-memory implementations, alongside a transaction-aware command sender for the taskpool.
77 changes
2022–2024 · Camunda integration and serialization
This period focused on deepening Camunda BPM integration by introducing auto-configuration, transactional job senders, and event mappers for task and process lifecycle management. Concurrently, the codebase standardized JSON serialization through a centralized Jackson configuration and expanded test coverage for both the bus and view modules.
23 changes
Survey your own repository
holunda-io/camunda-bpm-taskpool 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 29 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 9d990300f3 — 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.