An asynchronous Rust client for Valkey and Redis with support for RESP2/RESP3, clustering, TLS, and advanced features.
Fred is a high-performance, asynchronous Rust client library for interacting with Valkey and Redis servers. It provides a comprehensive, type-safe interface that supports modern Redis deployments, including clustered, centralized, and sentinel-based topologies, along with advanced features like pub/sub, client-side caching, and transactions.
Rust developers building high-concurrency applications that require reliable, low-latency communication with Redis or Valkey backends, such as real-time systems, caching layers, or message brokers.
Developers choose Fred for its emphasis on type safety, extensibility via compile-time feature flags, and performance optimizations like zero-copy frame parsing and connection pooling, making it suitable for demanding production environments.
An async client for Valkey and Redis
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built on Tokio with zero-copy frame parsing and connection pooling, ensuring low latency and high concurrency for demanding applications.
Supports both RESP2 and RESP3 serialization protocols, making it compatible with modern Redis and Valkey deployments.
Handles clustered, sentinel, and centralized deployments with automatic reconnection and TLS support for robust production use.
Provides a type-safe interface with compile-time feature flags to tailor the client to specific needs, reducing runtime errors.
Includes interfaces for pub/sub, client-side caching, transactions, and mocking, covering a wide range of Redis capabilities as shown in the README.
The extensive feature flags and interface modules can lead to significantly increased compile times, which may hinder rapid development cycles.
With numerous optional features like TLS backends, tracing levels, and interface flags, initial setup can be overwhelming and error-prone for new users.
Compared to established clients like redis-rs, Fred has a smaller community and fewer third-party integrations, which might limit support resources.