// the find
fluvio-community/fluvio
🦀 event stream processing for developers to collect and transform data in motion to power responsive data intensive applications.
Fluvio is a distributed stream processing engine written in Rust that combines a Kafka-like messaging layer with a WebAssembly-based transformation pipeline called Stateful DataFlow. It targets developers who want Kafka-style durability without running a JVM stack, and want stream transformations that are portable and sandboxed via WASM. Originally from InfinyOn, it's now community-maintained after what appears to be a company transition.
The WASM-based SmartModules are the genuinely interesting part — you write a transformation once, compile to WASM, and it runs inside the broker without a separate compute layer. The Rust core means memory-safe, low-overhead SPUs that don't need GC tuning. The CLI-first design (`fluvio topic create`, `fluvio produce`, `fluvio consume`) gives a tight local dev loop you can test in two minutes without a container. The Connector Development Kit is a real framework, not just a tutorial, with typed config, secrets handling, and a proper packaging format.
The company-to-community transition is a real adoption risk — the README has a 'TEMPORARY NOTE' about broken release infrastructure and tells you to install a dev build, which is not confidence-inspiring for anything production-adjacent. Stateful DataFlow (SDF) is a separate product with its own docs, examples repo, and pricing that isn't clearly delineated from the open-source core, so it's hard to tell what you actually get without hitting a paywall. Windows support is WSL2-only with no native path, which limits where you can run it. The community connector ecosystem is thin — a Google Sheets connector and an Elastic connector don't compete with Kafka's connector catalog.