Databases 2 min read

Rudis v0.2.0 Released – New Architecture, Master‑Slave Replication, and 99% Faster Keys

Rudis v0.2.0 introduces a major architecture overhaul, upgraded Tokio runtime, shared‑nothing threading, master‑slave replication, transaction support, and a refactored KEYS command that boosts performance by up to 99.55% for large data sets.

Laravel Tech Community
Laravel Tech Community
Laravel Tech Community
Rudis v0.2.0 Released – New Architecture, Master‑Slave Replication, and 99% Faster Keys

Release Overview

Rudis v0.2.0 is now officially available. The release adds major architectural upgrades, master‑slave replication, transaction support, enhanced scan commands, extended data‑structure operations, and stronger configuration management.

Architecture and Runtime

The underlying engine has been rebuilt. The Tokio asynchronous runtime is upgraded to version 1.48.0, leveraging newer async techniques for better performance and stability. The thread model switches from a shared‑everything design to a shared‑nothing architecture, significantly increasing concurrent processing capacity. Additionally, the RESP parser has been optimized to eliminate command‑sticky‑packet problems, ensuring reliable network transmission.

Key Command Performance

In this version the implementation of the KEYS command has been refactored. By redesigning data structures and query logic, performance on large data sets improves by up to 99.55%, dramatically reducing command execution time and providing a smoother user experience.

Rudis positions itself as a Redis‑compatible, modern‑stack, high‑performance key‑value storage solution.

databaseRedisAsynckey-value storeRudis
Laravel Tech Community
Written by

Laravel Tech Community

Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.