A high-performance Go framework for building Redis-protocol compatible TCP servers and services.
Redeo is a high-performance Go framework for building TCP servers and services that are compatible with the Redis Serialization Protocol (RESP). It solves the problem of creating custom, Redis-like servers by providing low-level protocol handling and a server framework, enabling developers to implement their own command sets and logic.
Go developers who need to build custom, high-performance services that communicate using the Redis protocol, such as those creating specialized data stores, proxies, or middleware.
Developers choose Redeo for its focused, minimalistic approach to Redis-protocol server development, offering essential building blocks without unnecessary bloat, and its emphasis on performance and flexibility in command handling.
High-performance framework for building redis-protocol compatible TCP servers/services
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Core package is optimized for building fast, Redis-protocol compatible TCP servers, as emphasized in the README's focus on performance and Swiss Army Knife philosophy.
Provides essential reader/writer implementations for RESP serialization on both client and server sides, enabling precise protocol handling without external dependencies.
Supports direct handler functions and wrapper functions for clean command processing, with examples showing middleware-like logic for custom execution flow.
Prioritizes simplicity and essential tools, avoiding bloat, which makes it lightweight and suitable for custom implementations without unnecessary overhead.
Unlike Redis itself, Redeo doesn't include any pre-defined commands; developers must implement all functionality from scratch, increasing development time and complexity.
The README provides basic examples but lacks comprehensive guides, advanced use cases, or troubleshooting resources, which could hinder learning and adoption.
Included client is minimalist and pooled, but it may not match the feature set of dedicated Redis client libraries like go-redis for complex operations or production-ready scenarios.