Skip to content

Commit 38319b6

Browse files
committed
Added merged additional PR
1 parent 6c5a847 commit 38319b6

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

articles/azure-cache-for-redis/quickstart-create-redis-enterprise.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.date: 04/07/2023
1414
The Azure Cache for Redis Enterprise tiers provide fully integrated and managed [Redis Enterprise](https://redislabs.com/redis-enterprise/) on Azure. These new tiers are:
1515

1616
* Enterprise, which uses volatile memory (DRAM) on a virtual machine to store data
17-
* Enterprise Flash, which uses both volatile and non-volatile memory (NVMe or SSD) to store data.
17+
* Enterprise Flash, which uses both volatile and nonvolatile memory (NVMe or SSD) to store data.
1818

1919
Both Enterprise and Enterprise Flash support open-source Redis 6 and some new features that aren't yet available in the Basic, Standard, or Premium tiers. The supported features include some Redis modules that enable other features like search, bloom filters, and time series.
2020

@@ -40,7 +40,7 @@ Azure Cache for Redis is continually expanding into new regions. To check the av
4040
| ------------ | ------- | -------------------------------------------------- |
4141
| **Subscription** | Drop down and select your subscription. | The subscription under which to create this new Azure Cache for Redis instance. |
4242
| **Resource group** | Drop down and select a resource group, or select **Create new** and enter a new resource group name. | Name for the resource group in which to create your cache and other resources. By putting all your app resources in one resource group, you can easily manage or delete them together. |
43-
| **DNS name** | Enter a name that is unique in the region. | The cache name must be a string between 1 and 63 characters that contain only numbers, letters, or hyphens. The name must start and end with a number or letter, and can't contain consecutive hyphens. Your cache instance's *host name* will be *\<DNS name\>.\<Azure region\>.redisenterprise.cache.azure.net*. |
43+
| **DNS name** | Enter a name that is unique in the region. | The cache name must be a string between 1 and 63 characters that contain only numbers, letters, or hyphens. The name must start and end with a number or letter, and can't contain consecutive hyphens. Your cache instance's *host name* is *\<DNS name\>.\<Azure region\>.redisenterprise.cache.azure.net*. |
4444
| **Location** | Drop down and select a location. | Enterprise tiers are available in selected Azure regions. |
4545
| **Cache type** | Drop down and select an *Enterprise* or *Enterprise Flash* tier and a size. | The tier determines the size, performance, and features that are available for the cache. |
4646

@@ -56,15 +56,18 @@ Azure Cache for Redis is continually expanding into new regions. To check the av
5656

5757
Enable **Non-TLS access only** if you plan to connect to the new cache without using TLS. Disabling TLS is **not** recommended, however.
5858

59-
Set **Clustering policy** to **Enterprise** for a non-clustered cache. For more information on choosing **Clustering policy**, see [Clustering Policy](#clustering-policy).
59+
Set **Clustering policy** to **Enterprise** for a nonclustered cache. For more information on choosing **Clustering policy**, see [Clustering Policy](#clustering-policy).
6060

6161
:::image type="content" source="media/cache-create/cache-clustering-policy.png" alt-text="Screenshot that shows the Enterprise tier Advanced tab.":::
6262

6363
> [!NOTE]
64-
> Enterprise and Enterprise Flash tiers are inherently clustered, in contrast to the Basic, Standard, and Premium tiers. Redis Enterprise supports two clustering policies. Use the **Enterprise** policy to access your cache using the regular Redis API. Use **OSS** to use the OSS Cluster API.
65-
>
64+
> Enterprise and Enterprise Flash tiers are inherently clustered, in contrast to the Basic, Standard, and Premium tiers. Redis Enterprise supports two clustering policies.
65+
>- Use the **Enterprise** policy to access your cache using the Redis API.
66+
>- Use **OSS** to use the OSS Cluster API.
67+
> For more information, see [Clustering on Enterprise](cache-best-practices-enterprise-tiers.md#clustering-on-enterprise).
68+
>
6669
67-
> [!NOTE]
70+
> [!IMPORTANT]
6871
> You can't change modules after you create the cache instance. The setting is create-only.
6972
>
7073
@@ -82,7 +85,7 @@ Azure Cache for Redis is continually expanding into new regions. To check the av
8285

8386
The OSS Cluster mode allows clients to communicate with Redis using the same Redis Cluster API as open-source Redis. This mode provides optimal latency and near-linear scalability improvements when scaling the cluster. Your client library must support clustering to use the OSS Cluster mode.
8487

85-
The Enterprise Cluster mode is a simpler configuration that exposes a single endpoint for client connections. This mode allows an application designed to use a standalone, or non-clustered, Redis server to seamlessly operate with a scalable, multi-node, Redis implementation. Enterprise Cluster mode abstracts the Redis Cluster implementation from the client by internally routing requests to the correct node in the cluster. Clients aren't required to support OSS Cluster mode.
88+
The Enterprise Cluster mode is a simpler configuration that exposes a single endpoint for client connections. This mode allows an application designed to use a standalone, or nonclustered, Redis server to seamlessly operate with a scalable, multi-node, Redis implementation. Enterprise Cluster mode abstracts the Redis Cluster implementation from the client by internally routing requests to the correct node in the cluster. Clients aren't required to support OSS Cluster mode.
8689

8790
## Next steps
8891

0 commit comments

Comments
 (0)