Skip to content

Redis

Overview

Nexaa now offers Redis as an experimental managed option. This experimental version provides insights into how Redis is used and helps deliver the best functionality in future releases.

Redis is a high-performance, in-memory data structure store used as a database, cache, and message broker. It's ideal for caching, session management, real-time analytics, and queue systems.

Current Implementation

The Redis offering provides:

  • Single-node Redis instance running in a container
  • Minimal resource allocation by default, but this can be changed
  • Optional persistence configuration
  • Similar management experience to MySQL and PostgreSQL offerings

Persistence Considerations

When creating your Redis instance, you can choose to enable or disable persistence:

Without Persistence (Lower Cost)

  • Use case: Caching purposes
  • Advantage: Lower pricing
  • Risk: Data loss on restart or failure
  • Best for: Applications where losing cache won't break functionality

Caching Use Case

Many applications use Redis for caching purposes. Losing cache will not break your application - it will simply rebuild the cache as needed.

With Persistence (Required for Data Storage)

  • Use case: Queues and data storage
  • Advantage: Data survives restarts and failures
  • Requirement: Essential for persistent data and queue systems
  • Best for: Message queues, session storage, and persistent data structures

Choose Based on Your Use Case

Whether you need persistence depends entirely on your use case. If Redis is storing critical data or managing queues, persistence is required. For pure caching, you can possibly disable it.

What to Expect in the Future

The final managed Redis cluster will be similar to our MySQL and PostgreSQL offerings:

  • Multi-node cluster configurations (1-node, 2-node, 3-node)
  • High availability and automatic failover
  • Enhanced monitoring and management tools
  • Production-grade reliability and performance

Getting Started

To create a Redis instance:

  1. Navigate to Cloud Databases in the Nexaa portal
  2. Select "Redis"
  3. Choose whether to enable persistence based on your use case
  4. Configure minimal resources to get started
  5. Deploy within your namespace

Limitations

  • Single-node only: No high availability or failover support
  • Implementation subject to change
  • Basic configuration: Minimal resource options by default
  • No cluster mode: Single instance only

Connecting to Your Redis Instance

By default, Redis instances are only accessible from within the same namespace. You can request external access in the portal.

Feedback Welcome

Your feedback on this feature is valuable. Share your experience and requirements at feedback.nexaa.io.