Elders/Cronus

Cronus is an event-sourcing framework that manages the lifecycle of aggregate roots, projections, and background jobs within a multi-tenant environment. It provides infrastructure for automatic updates, message processing, and data migration, while offering tools for integrity validation, fault handling, and distributed locking. The system supports cluster-based job execution, projection versioning, and comprehensive telemetry, all built on a modern .NET foundation.

This period focused on modernizing the framework's core architecture by introducing a robust event sourcing model with structured message headers, concurrency control, and integrity validation. The team refactored the message processing pipeline to support scoped workflows and added comprehensive test coverage for the new event store and middleware systems. Additionally, the project upgraded to .NET 8/9 and standardized build configurations to improve resilience and observability.

16 changes

This period focused on introducing comprehensive projection versioning and lifecycle management, allowing for the safe creation, rebuilding, and activation of new projection states. Concurrently, the framework modernized its core infrastructure by implementing automatic service discovery, async host startup ranking, and a new workflow execution model with structured diagnostics.

19 changes

This period focused on expanding the framework's capabilities for cluster-based job execution, event store index management, and projection rebuilding. It introduced new abstractions for job runners, heartbeat monitoring, and public event replay, while also adding comprehensive test coverage and performance benchmarks.

14 changes

The codebase introduced a new AutoUpdater aggregate and saga-based strategy to track and execute multiple concurrent auto-updates independently of the core version. Additionally, a DangerZone feature was added to allow safe tenant data wiping with protection for critical tenants, accompanied by corresponding test coverage.

4 changes

Elders/Cronus 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.