.. _storage:

.. relock documentation service file, created by
   sphinx-quickstart on Wed May 14 18:37:20 2025.
   You can adapt this file completely to your liking, but it should at least
   contain the root `toctree` directive.

Storage
-------

The choice of storage system depends on the deployment needs. The Relock service supports any Redis OSS-compatible solution, including Valkey, Memcached, KeyDB, and managed cloud services like Amazon ElastiCache. Each option offers different trade-offs in terms of performance, scalability, features, and operational complexity:

* Valkey: A fully open-source fork of Redis, created to maintain an open governance model after Redis adopted a source-available license. Valkey is compatible with Redis clients and is a solid choice for those who want to remain in the open-source ecosystem without vendor lock-in.

* Memcached: A lightweight, high-performance memory caching system. It supports simple key-value pairs and is well-suited for use cases where persistence, replication, or complex data structures aren't needed.

* KeyDB: A Redis-compatible database offering advanced features such as multi-threading, active-active replication, and built-in TLS support. It's a good option for applications requiring high throughput and enhanced performance without changing the Redis API.

* Amazon ElastiCache (for Redis or Memcached): A fully managed, scalable, and highly available in-memory data store service from AWS. ElastiCache removes the operational overhead of managing infrastructure, provides built-in monitoring and security, and is ideal for production environments needing reliability and ease of maintenance.

* Other cloud-based Redis-compatible services: Providers like Azure Cache for Redis, Google Memorystore, and Upstash offer similar managed Redis solutions with varying levels of scalability, regional availability, and pricing models.

When choosing a solution, consider factors such as required performance, operational overhead, cost, licensing preferences, and whether there's a preference to manage infrastructure directly or use a cloud-managed service.