Azure Cache for Redis

Azure Cache for Redis is Microsoft’s managed Redis service. ZopDay creates a cache from Infrastructure → Provision → Redis Cache and records its connection details in Key Vault.

What does an Azure Cache for Redis job create

The examples below use a cache called orders.

• A resource group, unless you pick an existing one. By default it is named after the cache, such as zop-orders.
• With Create new VPC, a virtual network (VNet) such as orders-vnet (10.0.0.0/16), with a subnet such as orders-nodes.
• A /24 subnet such as orders-db-subnet in the job’s VNet, new or existing. The cache itself is not placed in that network.
• The cache, on Redis version 6, with the non-TLS port turned off and a minimum of TLS 1.2.
• A Key Vault secret such as zop-ds-orders. It sits in a vault that ZopDay manages, in the same resource group.

1 node (default): SKU Standard, family C, capacity 1 (C1).
More than 1 node: SKU Premium, family P, capacity equal to the node count.
Endpoint: the cache name plus .redis.cache.windows.net (for example
orders.redis.cache.windows.net), port 6380.

Why is the Azure Redis node type choice ignored

You pick a Node type from a list that runs from C0 to P2, and the list starts on C0. On Azure, ZopDay ignores that choice. The size comes from the node count alone, as shown above.

Advanced settings has:

• Memory / Nodes (1 to 6, default 1);
• an engine version list with only 6.0;
• a Public Access toggle, which ZopDay does not apply on Azure;
• the resource group.

Why the stored Redis password is not the cache access key

The stored secret holds endpoint, port, username (zopadmin), password and database.

ZopDay generates the 32-character password on its own side and never sends it to Azure. So it is not the cache’s access key. When an application needs to sign in to the cache, read the access keys from the cache in Azure, for example with az redis list-keys.

How do clients reach the Azure Redis cache

ZopDay sets no private endpoint, VNet injection or firewall rules on the cache. Clients connect to the cache’s hostname over TLS on port 6380. Azure’s default network access settings for the cache apply.

How long does an Azure Redis cache take to create

Creating a cache can take many minutes. ZopDay keeps checking until Azure reports the cache ready. If the cache is still not visible after 25 minutes, that step of the job fails.

Which Azure Redis settings can an update job change

An update job can change the tier (Basic, Standard or Premium) and the capacity. ZopDay does not change the cache on its own.

What does deleting an Azure Redis job remove

Deleting the job first soft-deletes the Key Vault secret. ZopDay does not purge it, so it stays recoverable for the vault’s retention period. That is 90 days unless the vault was set up otherwise.

ZopDay then deletes the cache and the subnet it added for it (such as orders-db-subnet). If ZopDay created the network for this job, it removes that too. If ZopDay created the resource group, it deletes the whole group.