A Redis client for Deno, supporting commands, pub/sub, streams, clustering, and advanced features like pipelining and client-side caching.
deno-redis is a Redis client library for the Deno runtime, allowing Deno applications to connect to and interact with Redis databases. It solves the need for a native, secure Redis client in Deno by providing support for commands, pub/sub, streams, clustering, and advanced features like pipelining and client-side caching.
Deno developers building applications that require Redis for caching, real-time messaging, session storage, or stream processing. It's particularly useful for those leveraging Deno's security features and TypeScript ecosystem.
Developers choose deno-redis because it's the official Redis client for Deno, offering full Redis compatibility, modern TypeScript support, and integration with Deno's permission system. Its experimental features and active development provide a future-proof solution for Redis interactions in Deno.
🦕 Redis client for Deno 🍕
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports standard Redis commands, pub/sub, streams, and clustering with code examples in the README, such as xadd for streams and clusterMeet for node management.
Includes pipelining, transactional pipelines (TxPipeline), and client-side caching, demonstrated in the README with clear usage snippets for efficient data operations.
Built for Deno's TypeScript ecosystem, providing type-safe APIs and examples like stateless commands with async/await for seamless development.
Integrates with Deno's security model by requiring --allow-net permission, ensuring controlled network access as highlighted in the installation notes.
Labeled as an experimental implementation with features like connection pooling marked as experimental, risking API changes and limited production readiness.
As a Deno-specific client, it has a smaller community and fewer third-party integrations compared to established Node.js Redis libraries, which can hinder troubleshooting.
Configuring Redis clusters requires manual steps like using clusterMeet commands, as shown in the cluster example, adding complexity for developers.