Title here
Summary here
RapidRecast
Streaming made simple
Example GuideStreaming made simple
Example GuideCreate streams the way you want them: WebSockets, HTTP requests, Kafka, HTTP 2, HTTP 3, WebRTC, Spark, and many more.
Wire your components together and forget if they are services or clients. You can even use Cron Expressions to make 2 APIs stream to each other - without a background ticker publishing to RapidRecast.
Synchronous requests are so convenient! Why not use RapidRecast to keep that simplicity?
RapidRecast is built with scalability in mind. You won't need to explicitly declare partitions or shards. Just watch RapidRecast rebalance as replicas are added to the cluster.
If a single request takes 20ms, but a batch of 100 takes 30ms, then you would prefer to batch your requests, right? Gotcha fam.
Fans of Ferris and followers of Crabulon will agree this is exciting. Rust brings performance and memory-safety to RapidRecast, and underpins what makes this software so fast.
Integration is scary. That is why RapidRecast tries to keep things simple. You should be able to simply point your endpoints at the service and start streaming.
RapidRecast is rigorously tested, the same way databases are. Randomised tests explore any possible edge cases, while also validating correctness of data.