Roadmap

What's next on the path to StoatFlow 1.0 — and beyond.

Items are grouped by status, not by date. Each piece ships when it's production-ready, alongside the benchmarks and changelog entry that go with it. Order within each section reflects current priority.

In progress

Active development — landing in upcoming alpha and beta releases.

  • Maven plugin — Build conventions for Maven users, mirroring the existing io.stoatflow Gradle plugin.
  • Side outputs — Flink-style multi-output processors. Emit secondary streams from a single processor step without re-keying.
  • Async IO processor — Non-blocking external lookups (HTTP, RPC, database) with bounded concurrency and ordered output, designed for enrichment workflows.

Planned

Approved direction; scheduled into upcoming milestones.

  • Multi-table joins — Joining a stream against multiple state stores in a single processor, replacing the current chain-of-binary-joins pattern.
  • Advanced state-store caching — Tiered caches with configurable eviction. Reduces RocksDB read pressure on hot keys.
  • Dispatch tiers — Source-level priority for topologies that mix live and bulk workloads. Background reloads (e.g. master-data refreshes) defer to live traffic, so a 100M-row bulk load doesn't stall live-side window closures or SLAs.
  • Hot standby & blue-green deployments — Warm secondary instance for zero-downtime rollouts and faster recovery.
  • Migration tooling — Drop-in adapters and migration playbooks for teams moving from Kafka Streams.
  • Expanded benchmarks — Additional workload classes — windowed aggregations, foreign-key joins, async enrichment — on heterogeneous hardware.

Exploring

On the radar; design and scope still being assessed.

  • Framework integrations — First-class modules for Spring, Micronaut, and Quarkus.

Have a use case that depends on something not listed? Get in touch — roadmap priority follows real customer demand.