DLEZ
Skip to documentation
Documentation menu · Redis

Products

Redis

Managed Redis for caching, sessions and rate limiting without setting up a Redis server.

On this page

When to use it

Use Redis for frequently read cache data, sessions, rate limits and compatible pub/sub or lightweight queue workloads. Check the commands required by your client or queue library before production; managed Redis restricts administrative commands.

Console and limits

Connection provides host, port, username and password. Metrics show commands, bandwidth, storage and connections. Check your plan's command rate, monthly quotas and connection limits; do not assume every library is compatible.

Connecting your app

Products in the same DLEZ organization communicate through private endpoints, including products in different projects. Use the destination service's private host and port. Your laptop and browser are external clients even when you are signed in to Console; use a public endpoint for external access. Keep credentials on the server and follow the service's TLS requirements.

Step by step

  1. Open Database > Redis, name the service and choose a plan for commands, capacity, bandwidth and connections.
  2. Wait until ready. Copy its private host/port and credentials from Connection for an app in the same org; use public access for external clients.
  3. Install your Redis client and configure the endpoint and TLS as required by the service. Test the connection before adding cache logic.
  4. Run SET docs:hello dlez EX 60, then GET docs:hello. Expect dlez and expiration after about 60 seconds.
  5. In your code, read cache first; on a miss, fetch source data and cache it with a TTL. Invalidate or update affected keys when the source data changes.
  6. Monitor usage and client compatibility. Keep primary data in durable storage with its own recovery plan.