base on Lean and mean distributed stream processing system written in rust and web assembly. Alternative to Kafka + Flink in one. <div align="center"> <h1>Fluvio</h1> <a href="https://fluvio.io" target="_blank"> <strong>Composable, Declarative, Stateful Data Streaming System</strong> </a> <br> <br> [](https://github.com/infinyon/fluvio/actions/workflows/hourly.yml) [](https://github.com/infinyon/fluvio/actions/workflows/cd_dev.yaml) [](https://crates.io/crates/fluvio) [](https://docs.rs/fluvio) [](https://deps.rs/repo/github/infinyon/fluvio) [](https://discordapp.com/invite/bBG2dTz) <br> [](https://fluvio.io) <br> </div> **Fluvio** is a lean and mean distributed data streaming engine written in Rust. Combined with **Stateful DataFlow** distributed stream processing framework, Fluvio provides a *unified* *composable* *distributed streaming* and *stream processin*g paradigm for developers. It is the foundation of [InfinyOn Cloud](https://infinyon.cloud/). ## Quick Start - Get started with Fluvio and Stateful DataFlow in 5 minutes or less on your system! ### Step 1. Download Fluvio Version Manager: Fluvio is installed via the **Fluvio Version Manager**, shortened to `fvm`. To install `fvm`, run the following command: ```bash curl -fsS https://hub.infinyon.cloud/install/install.sh | bash ``` As part of the initial setup, `fvm` will also install the Fluvio CLI available in the stable channel as of the moment of installation. Fluvio is stored in `$HOME/.fluvio`, with the executable binaries stored in `$HOME/.fluvio/bin`. > For the best compatibliity on Windows, InfinyOn recommends WSL2 ### Step 2. Start a cluster: Start cluster on you local machine with the following command: ```bash fluvio cluster start ``` ### Step 3. Install SDF CLI Stateful dataflows are managed via `sdf cli` that we install it using `fvm`. ```bash fvm install sdf-beta4 ``` ### Step 4. Create the Dataflow file Create a dataflow file in the directory `split-sentence` directory: ```bash mkdir -p split-sentence-inline cd split-sentence-inline ``` Create the `dataflow.yaml` and add the following content: ```yaml apiVersion: 0.5.0 meta: name: split-sentence-inline version: 0.1.0 namespace: example config: converter: raw topics: sentence: schema: value: type: string converter: raw words: schema: value: type: string converter: raw services: sentence-words: sources: - type: topic id: sentence transforms: - operator: flat-map run: | fn sentence_to_words(sentence: String) -> Result<Vec<String>> { Ok(sentence.split_whitespace().map(String::from).collect()) } - operator: map run: | pub fn augment_count(word: String) -> Result<String> { Ok(format!("{}({})", word, word.chars().count())) } sinks: - type: topic id: words ``` ### Step 5. Run the DataFlow Use sdf command line tool to run the dataflow: ```bash sdf run --ui ``` > The --ui flag serves the graphical representation of the dataflow on SDF Studio. ### Step 6. Test the DataFlow Produce sentences to in `sentence` topic: ```bash fluvio produce sentence ``` Input some text, for example: ```bash Hello world Hi there ``` Consume from `words` to retrieve the result: ```bash fluvio consume words -Bd ``` See the results, for example: ```bash Hello(1) world(1) Hi(1) there(1) ``` ### Step 6. Inspect State The dataflow collects runtime metrics that you can inspect in the runtime terminal. Check the sentence-to-words counters: ```bash show state sentence-words/sentence-to-words/metrics ``` See results, for example: ```bash Key Window succeeded failed stats * 2 0 ``` Check the augment-count counters: ```bash show state sentence-words/augment-count/metrics ``` See results, for example: ```bash Key Window succeeded failed stats * 4 0 ``` Congratulations! You've successfully built and run a composable dataflow! More examples of Stateful DataFlow are on GitHub - https://github.com/infinyon/stateful-dataflows-examples/. #### Check Fluvio Core Documentation Fluvio documentation will provide additional context on how to use the Fluvio clusters, CLI, clients, a development kits. - [Fluvio overview](https://www.fluvio.io/docs/fluvio/overview) - [Fluvio CLI docs home](https://www.fluvio.io/docs/fluvio/cli/overview) - [Fluvio Architecture](https://www.fluvio.io/docs/fluvio/concepts/architecture/overview) #### Check Stateful DataFlow Documentation Stateful DataFlow designed to handle complex data processing workflows, allowing for customization and scalability through various programming languages and system primitives. - [SDF overview](https://www.fluvio.io/sdf/) - [SDF Architecture](https://www.fluvio.io/sdf/concepts/architecture) #### Learn how to build custom connectors Fluvio can connect to practically any system that you can think of. - For first party systems, fluvio clients can integrate with the edge system or application to source data. - For third party systems fluvio connectors connect at the protocol level and collects data into fluvio topics. Out of the box Fluvio has native http, webhook, mqtt, kafka inbound connectors. In terms of outbound connectors out of the box Fluvio supports http, SQL, kafka, and experimental builds of DuckDB, Redis, S3, Graphite etc. Using Connector Development Kit, its intuitive to build connectors to any system fast. Check out the docs and let us know if you need help building any connector. - [Connector docs](https://www.fluvio.io/docs/connectors/overview) - [Connector Development Kit (cdk) docs](https://www.fluvio.io/docs/connectors/cdk) #### Learn how to build custom smart modules Fluvio applies wasm based stream processing and data transformations. We call these reusable transformation functions smart modules. Reusable Smart modules are built using Smart Module Development Kit and can be distributed using InfinyOn Cloud hub. - [Smart Modules docs](https://www.fluvio.io/docs/smartmodules/overview) - [Smart Modules Development Kit (smdk) docs](https://www.fluvio.io/docs/smartmodules/smdk) #### Try workflows on InfinyOn Cloud InfinyOn Cloud is Fluvio on the cloud as a managed service. - [Check InfinyOn Cloud Guides](https://infinyon.com/docs/guides/) - [Check out experimental data flows on InfinyOn Labs Repo](https://github.com/infinyon/labs-projects) ### Clients - [Fluvio Client API docs home](https://www.fluvio.io/docs/fluvio/apis/overview) **Language Specifc API docs:** - [Rust API docs](https://docs.rs/fluvio/latest/fluvio/) - [Python API docs](https://infinyon.github.io/fluvio-client-python/fluvio.html) - [Javascript API docs](https://infinyon.github.io/fluvio-client-node/) **Community Maintained:** - [Go API docs](https://github.com/avinassh/fluvio-go) - [Java API docs](https://github.com/infinyon/fluvio-client-java) - [Elixir API docs](https://github.com/viniarck/fluvio-ex) ## Contributing If you'd like to contribute to the project, please read our [Contributing guide](CONTRIBUTING.md). ## Community Many fluvio users and developers have made projects to share with the community. Here a a few listed below: ### Projects Using Fluvio - [Swiftide Project](https://github.com/bosun-ai/swiftide): a Rust native library for building LLM applications - [Real Time Stock Charts](https://github.com/KeptCodes/stock-charts): See how Fluvio is used to update real time stock charts ### Community Connectors - [Qdrant Connector](https://qdrant.tech/documentation/data-management/fluvio/) - [Google Sheets Connector](https://github.com/fluvio-connectors/sheets-connector): Send data from Fluvio to Google Sheets - [Elastic Connector](https://github.com/fluvio-connectors/elastic-connector): Send data from Fluvio to Elastic Search ## Community Development Resources More projects and utilities are available in the [Fluvio Community Github Org](https://github.com/fluvio-community/) - [Hello World Fluvio Connector](https://github.com/fluvio-community/connector-hello-source): Sample Fluvio connector template to build your own connector - [Gurubase](https://gurubase.io/g/fluvio): Third-party AI/LLM Docs query ### Contributors are awesome <a href="https://github.com/infinyon/fluvio/graphs/contributors"> <img src="https://contrib.rocks/image?repo=infinyon/fluvio" /> </a> Made with [contrib.rocks](https://contrib.rocks). ## License This project is licensed under the [Apache license](LICENSE). ", Assign "at most 3 tags" to the expected json: {"id":"3084","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"