<antirez>
7 hours ago
- Redis creator initially avoided modules due to concerns about API compatibility and system identity.
- Lua scripting was insufficient for extending Redis beyond its core capabilities.
- Direct exposure of internal APIs to modules leads to fragility and evolution problems.
- A new modules API was prototyped to ensure binary and API compatibility across versions.
- The API provides low-level access to Redis data structures, enabling native-speed commands.
- An example module implementing 'list splice' is shown, with automatic memory management.
- Modules will be stable in Redis 4.0 with backward compatibility guaranteed.
- A modules directory and community-driven ranking system are planned.
- The API is still malleable and open for feedback.