ChronoFlow is a modular event-driven backend platform built with .NET.
The goal of ChronoFlow is to provide a clean foundation for building event-sourced systems, orchestration platforms, and scalable backend services.
This project follows strict architectural boundaries to ensure the core remains reusable across multiple domains.
Evolution isn’t deviation. It’s convergence.
ChronoFlow is built as a Modular Monolith.
A single deployable API with strict internal module boundaries.
ChronoFlow ├── ChronoFlow.Api ├── ChronoFlow.Core ├── ChronoFlow.Infrastructure ├── ChronoFlow.Modules.Identity ├── ChronoFlow.Modules.Events └── ChronoFlow.Tests
Each module owns its domain logic while the core remains domain-agnostic.
A critical rule of the platform:
Domain logic must never leak into the core.
- User registration
- JWT authentication
- Protected endpoints
- Event ingestion endpoint
- Event stream querying
- Chronological ordering
- Stream isolation
- Unit tests for application logic
- Integration tests against the API
- Test-driven validation of event behavior
POST /auth/register
POST /auth/login
POST /events
ChronoFlow is built with:
- .NET
- ASP.NET Core
- PostgreSQL
- Entity Framework Core
- xUnit testing
ChronoFlow follows strict engineering rules:
- Write tests before shipping features.
- Keep the core reusable and domain-agnostic.
- Modules must not leak domain logic into the platform core.
- Architecture must remain evolvable without rewrites.
ChronoFlow is currently in early development.
Completed:
- Identity module
- Event ingestion
- Event stream queries
- Integration testing
Planned:
- Event dispatch pipeline
- Projection system
- Workflow orchestration
- distributed processing
Apache License 2.0