Skip to content

Commit 15d9c3e

Browse files
Merge pull request #233217 from MSFTeegarden/patch-20
Added Enterprise content
2 parents ae8c536 + e069c4f commit 15d9c3e

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

articles/azure-cache-for-redis/cache-best-practices-development.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Some Redis operations, like the [KEYS](https://redis.io/commands/keys) command,
6262

6363
## Choose an appropriate tier
6464

65-
Use Standard or Premium tier for production systems. Don't use the Basic tier in production. The Basic tier is a single node system with no data replication and no SLA. Also, use at least a C1 cache. C0 caches are only meant for simple dev/test scenarios because:
65+
Use Standard, Premium, Enterprise, or Enterprise Flash tiers for production systems. Don't use the Basic tier in production. The Basic tier is a single node system with no data replication and no SLA. Also, use at least a C1 cache. C0 caches are only meant for simple dev/test scenarios because:
6666

6767
- they share a CPU core
6868
- use little memory
@@ -89,6 +89,10 @@ The public IP address assigned to your cache can change as a result of a scale o
8989

9090
The default version of Redis that is used when creating a cache can change over time. Azure Cache for Redis might adopt a new version when a new version of open-source Redis is released. If you need a specific version of Redis for your application, we recommend choosing the Redis version explicitly when you create the cache.
9191

92+
## Specific guidance for the Enterprise tiers
93+
94+
Because the _Enterprise_ and _Enterprise Flash_ tiers are built on Redis Enterprise rather than open-source Redis, there are some differences in development best practices. See [Best Practices for the Enterprise and Enterprise Flash tiers](cache-best-practices-enterprise-tiers.md) for more information.
95+
9296
## Use TLS encryption
9397

9498
Azure Cache for Redis requires TLS encrypted communications by default. TLS versions 1.0, 1.1 and 1.2 are currently supported. However, TLS 1.0 and 1.1 are on a path to deprecation industry-wide, so use TLS 1.2 if at all possible.
@@ -149,7 +153,7 @@ If your application validates certificate in code, you need to modify it to reco
149153

150154
For more information, see [Client libraries](cache-best-practices-client-libraries.md#client-libraries).
151155

152-
## Next steps
156+
## Next steps
153157

154158
- [Performance testing](cache-best-practices-performance.md)
155159
- [Failover and patching for Azure Cache for Redis](cache-failover.md)

0 commit comments

Comments
 (0)