Apache Iggy, a message streaming platform in Rust, graduates to an Apache TLP
1–10 of 35 posts
Re: Apache Iggy, a message streaming platform in Rust, graduates to an Apache TLP
#2It’s been quite a journey, from a small Rust message-streaming experiment in 2023 to an independent Apache project with a growing community. And its biggest feature yet, being the Viewstamped Replication Revisited (VSR) clustering, is coming soon.
Re: Apache Iggy, a message streaming platform in Rust, graduates to an Apache TLP
#3Re: Apache Iggy, a message streaming platform in Rust, graduates to an Apache TLP
#4Is this a MQ implementation, or can this be used in place of e.g. something like protobufs and iroh/tonic? Does it have something akin to grants/capabilities/authorization? Does it have RPC? Can I have services speak a more privileged set of instructions/commands and clients needing auth to speak dumber/more high level administrative commands just like gRPC?
Also, is the performance due to the (what I assume is custom) zero copy serialization?
The landing page simply states it's essentially "fast messaging" but beyond that it's not entirely clear when I'd use this or what its features/limitations are.
Re: Apache Iggy, a message streaming platform in Rust, graduates to an Apache TLP
#5I always thought Im just not good enough to understand, hey Im just too dumb, surely there's people out there who understand what differentiates all these apache products! Nope never found one.
Re: Apache Iggy, a message streaming platform in Rust, graduates to an Apache TLP
#6I always thought Im just not good enough to understand, hey Im just too dumb, surely there's people out there who understand what differentiates all these apache products! Nope never found one.
Re: Apache Iggy, a message streaming platform in Rust, graduates to an Apache TLP
#7Re: Apache Iggy, a message streaming platform in Rust, graduates to an Apache TLP
#8Re: Apache Iggy, a message streaming platform in Rust, graduates to an Apache TLP
#9I believe spetz is on the project, so I'd like to ask: Is this a MQ implementation, or can this be used in place of e.g. something like protobufs and iroh/tonic? Does it have something akin to grants/capabilities/authorization? Does it have RPC? Can I have services speak a more privileged set of instructions/commands and clients needing auth to speak dumber/more high level administrative commands just like gRPC? Also…
There are a bunch of things that sum up to the overall performance gains - using Rust, thread-per-core architecture + shared-nothing (think of Seastar), custom zero-copy serialization, io_uring for disk * network I/O, and VSR-based consensus (inspired by TigerBeetle) - we simply build all this stuff from the ground up to make the most out of modern hardware and Kernel features, with a custom protocol on top (but the Kafka proxy/gateway is also WiP). And there are also connectors (sink, source), benchmarking runtime, CLI and so on.
Re: Apache Iggy, a message streaming platform in Rust, graduates to an Apache TLP
#10I love my Italian Greyhounds so much, so this is great news to me.