A full-featured, high-performance Redis client library for the Crystal programming language.
crystal-redis is a feature-complete Redis client library for the Crystal programming language. It provides a high-performance, idiomatic interface to Redis, allowing Crystal developers to interact with Redis databases using all standard commands and advanced features like pipelining and transactions. It solves the need for a reliable, native Redis driver in the Crystal ecosystem.
Crystal developers building applications that require Redis for caching, real-time features, message brokering, or as a primary data store. It's particularly valuable for web applications using frameworks like Kemal that need concurrent Redis access.
Developers choose crystal-redis for its exceptional performance (benchmarked faster than equivalent C and Ruby clients), comprehensive command support, and built-in connection pooling for concurrent safety. It's the de facto standard Redis client for Crystal, offering production-ready reliability and excellent documentation.
Full featured Redis client for Crystal
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Benchmarked at over 680,000 commands per second with pipelining, outperforming C and Ruby clients in the author's 2015 tests.
Supports all major command categories from strings to geo commands and pub/sub, ensuring full compatibility with Redis features.
Redis::PooledClient provides connection pooling out of the box, essential for safe concurrent access in web frameworks like Kemal, as noted in the README.
Extensively spec-tested with real usage examples and community reports of production deployment, indicating high stability.
Installation on MacOS X requires manual steps like installing openssl via Homebrew and setting PKG_CONFIG_PATH, as admitted in the README.
Tied to Crystal's smaller adoption, which limits community support, long-term maintenance, and integration options compared to clients for mainstream languages.
Key benchmarks are from a 2015 blog post, potentially not reflecting current Redis versions or competitive client improvements.