Summary

Lux addresses the performance ceiling of Redis's single-threaded architecture by providing a Redis-compatible key-value store built with a multi-threaded, sharded Rust design. It targets users needing higher throughput and lower latency, offering up to 10x faster performance and linear scalability across multiple CPU cores, while integrating advanced features like native vector search and time series data.

How It Works

Lux employs a sharded concurrent architecture leveraging Rust and Tokio's async runtime. Each key maps to a shard protected by a parking_lot RwLock, enabling reads to proceed concurrently and writes to affect only a single shard. This design safely utilizes all available CPU cores within a single process, achieving linear throughput scaling unlike Redis's single-core limitation. Transactions (MULTI/EXEC) utilize optimistic concurrency via shard versioning, avoiding global locks.

Quick Start & Requirements

• Installation: Build from source using cargo build --release or use the Docker image ghcr.io/lux-db/lux:latest.
• Prerequisites: Rust toolchain for source builds.
• Documentation: Architecture deep dive available at luxdb.dev/architecture.

Highlighted Details

• Performance: Benchmarks show up to 10x higher throughput than Redis 8.4.2, particularly for pipelined commands and GEO searches, with linear scaling as cores are added.
• Native Features: Integrates vector search (cosine similarity, HNSW), time series (aggregation, retention), realtime key subscriptions (KSUB), relational tables (typed fields, joins), and GEO commands directly, without requiring modules.
• Client Compatibility: Fully compatible with existing Redis RESP2 clients, requiring zero code changes for most workloads.
• Architecture: Utilizes a multi-threaded, sharded design with zero-copy parsing and pipeline batching for efficiency.

Maintenance & Community

The README does not detail specific community channels (e.g., Discord, Slack), notable contributors, or sponsorships.

Licensing & Compatibility

• License: MIT.
• Compatibility: Permissive MIT license allows for commercial use and integration into closed-source applications.

Limitations & Caveats

Lux omits AOF persistence in favor of snapshots and a 1-second-interval WAL, implying potential data loss up to that window. It supports only the RESP2 protocol and operates as a single-node system, with clustering managed via Lux Cloud. MULTI/EXEC transactions use optimistic locking, allowing other clients to observe intermediate states during execution, a difference from Redis's single-threaded isolation.