Replies: 1 comment
-
Thanks for the question @kharabela I creates a similar image comparing NATS, Kafka, and Fluvio. Going to use it to update our documentation. In terms of Delivery Guarantees Fluvio supports at least once, at most once, and we support indempotence using deduplication which delivers the same output as exactly once - https://www.fluvio.io/docs/concepts/delivery-semantics/ Fluvio also supports ordering guarantees, persistence, replay-ability - https://www.fluvio.io/docs/concepts/data-consistency/ Throughput assumes a number of partitions and Fluvio can scale up to Kafka level throughputs while consuming a fraction of compute and memory. On top of that the latest Stateful Services Development Kit enables stateful stream processing with offsets, states, and window based aggregations. Hope this answers your question. Please let me know if you have any follow up. |
Beta Was this translation helpful? Give feedback.
-
Could you share some metrics based on throughput for fluvio?
Beta Was this translation helpful? Give feedback.
All reactions