RillFlow
Project

The Problem

Event sourcing and CQRS are powerful patterns for building auditable, resilient systems—but the tooling has historically been heavyweight, enterprise-flavoured, and intimidating for small teams. Most frameworks assume a dedicated platform team and a sprawling infrastructure budget. I wanted the opposite: the durability guarantees of event sourcing with the ergonomics of writing an ordinary Rust service.

The Approach

RillFlow treats the event log as the single source of truth and gives you the primitives to build on top of it without ceremony.

• Append-only by design: Every state change is an immutable event, giving you a complete audit trail and the ability to rebuild state from history.
• Projections as first-class citizens: Derive read models from the event stream with a clear, testable API—no bolt-on glue code.
• PostgreSQL-native: Uses a database teams already run and trust as the event store, rather than demanding new infrastructure.
• Async from the ground up: Built on Tokio for high-throughput, non-blocking event processing.

The Philosophy

Resilient architecture shouldn't be a luxury reserved for companies with platform teams. RillFlow is my attempt to take patterns I rely on when building production SaaS and package them so a solo founder or a two-person team can adopt them in an afternoon. It is developed in the open, and the design decisions are documented as the framework evolves.

Status

RillFlow is actively developed and open source. Contributions, issues, and design discussions are welcome.