This Week in Fluvio #58
Fluvio is a distributed, programmable streaming platform written in Rust.
We paused the weekly updates because we had several big changes in flight. We will refactor this blog to Fluvio Release Updates and remove the weekly cadence in the next iteration.
A lot has happened in the past couple of months that is relevant to update.
Fluvio moved to version 0.11.3 a couple of days ago. We have had a bunch of releases since we last published an update on our site.
Full Changelog of the release is here: Fluvio Changelog
Fluvio has a bunch of exciting updates. The community has been asking for a single binary deployment that can be run locally, using Docker, using Nomad. That meant we needed to decouple our tigh coupling with Kubernetes. We did that in 2023 and the community started building with Fluvio!
We have been busy making documentation updates since then. So this update was delayed. Below are the main updates:
- Fluvio now has a version manager that manages multiple versions, installs, updates, etc. We are calling it Fluvio Version Manager(fvm)
- fvm can be installed by simply running:
curl -fsS https://hub.infinyon.cloud/install/install.sh | bash
- You can deploy Fluvio as a single compiled binary using fvm. The installer takes care of everything!
- You can run a local self-hosted Fluvio cluster by simply running
fluvio cluster start
which will start a self hosted fluvio clsuter using local resources
In light of this our Quick Start docs has been updated to reflect the changes. Getting started with fluvio is the easiest it has ever been.
There are some exciting community projects that are in development:
- There are some awesome new contributions in the works which inclused integrations with Spider Web Crawler, OpenSearch, ElasticSearch, Qdrant, Surreal, OpenDAL etc.
- We have an oversubscribed developer preview for Stateful Service Development Kit which makes stateful stream processing a reality.
- We have docs on docker based deployment. Link
If you are excited to contribute to Fluvio Open Source, here are 3 good first issues that you can consider:
- connector: fluvio-http-source, add an option to read data from a websocket
- MQTT Connector: Prefix auto generated Client ID to prevent connection drops
- fluvio cluster delete should prompt with cluster and endpoint name confirmation
All the best.
Get in touch with us on Github Discussions or join our Discord channel and come say hello!