flipkart-incubator/flux
Flux is an asynchronous, scalable state machine orchestrator that manages the lifecycle of distributed workflows. It provides a client-side framework for defining and intercepting tasks, while the runtime handles execution, event scheduling, and persistence. The system supports versioned workflow executions, dynamic deployment unit hot-swapping, and automated redriving of stalled tasks.
34.7
Weak · 29 July 2026
32k
lines of production code
Java
with JavaScript
3
bus factor · 27 authors in all
3
measurements over time
How it got here
2016 · initial project scaffolding and architecture
This period marks the initial scaffolding and architectural foundation of the Flux project, establishing a multi-module Maven build and defining core domain models for workflow execution and state machines. The work introduced the runtime, client, and API layers, including dashboard visualizations, dynamic deployment unit management, and client-side interception frameworks. Comprehensive test coverage was added across all modules to validate the new persistence services, routing utilities, and workflow execution logic.
54 changes
2017–2021 · Scheduler and persistence infrastructure
This period focused on implementing a comprehensive event and message scheduling system, including database schemas, DAOs, and services for managing scheduled tasks. It also introduced sharding support for entity persistence and added various utility classes and example workflows to demonstrate new capabilities like event replay and cancellation.
22 changes
2022 · state machine persistence layer
This period focused on building a new, isolated persistence module to manage state machine execution data. It introduced a comprehensive set of DAOs, managers, and query criteria to handle state machine entities, including support for database migrations and efficient storage of large objects.
6 changes
Survey your own repository
flipkart-incubator/flux 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 6ba29e520d — 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.