Skip to content

Commit 86d1d6a

Browse files
authored
Merge pull request #301924 from flang-msft/fxl---remove-template-samples
fxl---removed templating samples
2 parents 366cf26 + 53e28be commit 86d1d6a

13 files changed

+21
-457
lines changed

articles/azure-cache-for-redis/TOC.yml

Lines changed: 1 addition & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -238,12 +238,6 @@
238238

239239
- name: Samples
240240
items:
241-
- name: Use Azure Functions triggers and bindings
242-
items:
243-
- name: Create a simple Function app for Redis triggers
244-
href: /azure/redis/tutorial-functions-getting-started
245-
- name: Using Azure Functions to create a write-behind cache
246-
href: /azure/redis/tutorial-write-behind
247241
- name: Use Azure Kubernetes Service with a cache
248242
items:
249243
- name: Connect an AKS application to a cache
@@ -264,10 +258,7 @@
264258
items:
265259
- name: Use ASP.NET core output cache
266260
href: /azure/redis/aspnet-core-output-cache-provider
267-
- name: Use session state provider
268-
href: /azure/redis/aspnet-session-state-provider
269-
- name: Use output cache provider
270-
href: /azure/redis/aspnet-output-cache-provider
261+
271262
- name: Java Spring
272263
items:
273264
- name: Use Spring Boot Initializer
@@ -280,14 +271,6 @@
280271
href: cache-event-grid-quickstart-cli.md
281272
- name: Route events with PowerShell
282273
href: cache-event-grid-quickstart-powershell.md
283-
- name: Create leaderboards
284-
href: /azure/redis/web-app-cache-aside-leaderboard
285-
- name: Create Web App with Redis cache - Bicep
286-
displayName: ARM, Resource Manager, Template
287-
href: /azure/redis/web-app-bicep-with-redis-cache-provision
288-
- name: Create Web App with Redis cache - ARM template
289-
displayName: Resource Manager
290-
href: /azure/redis/web-app-arm-with-redis-cache-provision
291274

292275
- name: Reference
293276
items:

articles/azure-cache-for-redis/cache-troubleshoot-timeouts.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -114,10 +114,6 @@ In the following example, `retryTimeoutInMilliseconds` is set to `3000`.
114114
>
115115
```
116116

117-
For more information, see:
118-
- [ASP.NET Session State Provider for Azure Cache for Redis](/azure/redis/aspnet-session-state-provider)
119-
- [ASP.NET Output Cache Provider for Azure Cache for Redis](/azure/redis/aspnet-output-cache-provider)
120-
121117
### TCP settings for Linux based client applications
122118

123119
Client applications hosted on Linux could experience connectivity issues because of optimistic TCP settings in Linux. For more information, see [TCP settings for Linux-hosted client applications](cache-best-practices-connection.md#tcp-settings-for-linux-hosted-client-applications).

articles/azure-resource-manager/bicep/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -248,8 +248,6 @@ items:
248248
href: ../../api-management/quickstart-bicep.md?toc=/azure/azure-resource-manager/bicep/toc.json
249249
- name: Notification Hubs
250250
href: ../../notification-hubs/create-notification-hub-bicep.md?toc=/azure/azure-resource-manager/bicep/toc.json
251-
- name: Redis Web App
252-
href: ../../redis/web-app-bicep-with-redis-cache-provision.md?toc=/azure/azure-resource-manager/bicep/toc.json
253251
- name: SignalR Service
254252
href: ../../azure-signalr/signalr-quickstart-azure-signalr-service-bicep.md?toc=/azure/azure-resource-manager/bicep/toc.json
255253
- name: Concepts

articles/azure-resource-manager/templates/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -286,8 +286,6 @@ items:
286286
href: ../../app-service/quickstart-arm-template.md?toc=/azure/azure-resource-manager/templates/toc.json
287287
- name: Notification Hubs
288288
href: ../../notification-hubs/create-notification-hub-template.md?toc=/azure/azure-resource-manager/templates/toc.json
289-
- name: Redis Web App
290-
href: ../../redis/web-app-arm-with-redis-cache-provision.md?toc=/azure/azure-resource-manager/templates/toc.json
291289
- name: SignalR Service
292290
href: ../../azure-signalr/signalr-quickstart-azure-signalr-service-arm-template.md?toc=/azure/azure-resource-manager/templates/toc.json
293291
- name: Concepts

articles/redis/.openpublishing.redirection.redis.json

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,10 +46,20 @@
4646
"redirect_url": "../../aspnet/core/performance/caching/overview",
4747
"redirect_document_id": false
4848
},
49-
{
49+
{
5050
"source_path_from_root": "/articles/redis/web-app-cache-aside-leaderboard.md",
5151
"redirect_url": "../../aspnet/core/performance/caching/overview",
5252
"redirect_document_id": false
53+
},
54+
{
55+
"source_path_from_root": "/articles/redis/web-app-arm-with-redis-cache-provision.md",
56+
"redirect_url": "/azure/redis/redis-cache-arm-provision",
57+
"redirect_document_id": false
58+
},
59+
{
60+
"source_path_from_root": "/articles/redis/web-app-bicep-with-redis-cache-provision.md",
61+
"redirect_url": "/azure/redis/redis-cache-bicep-provision",
62+
"redirect_document_id": false
5363
}
5464
]
5565
}

articles/redis/TOC.yml

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -220,13 +220,6 @@ items:
220220
items:
221221
- name: Use Spring Boot Initializer
222222
href: /azure/developer/java/spring-framework/configure-spring-boot-initializer-java-app-with-redis-cache
223-
- name: Create Web App with Redis cache - Bicep
224-
displayName: ARM, Resource Manager, Template
225-
href: web-app-bicep-with-redis-cache-provision.md
226-
- name: Create Web App with Redis cache - ARM template
227-
displayName: Resource Manager
228-
href: web-app-arm-with-redis-cache-provision.md
229-
230223
- name: Reference
231224
items:
232225
- name: .NET

articles/redis/aspnet-core-output-cache-provider.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -171,5 +171,4 @@ It's a security best practice to avoid storing passwords in clear text in source
171171
172172
## Related content
173173
174-
- [ASP.NET Output Cache Provider for Azure Cache for Redis](aspnet-output-cache-provider.md)
175174
- [Output caching](/aspnet/core/performance/caching/overview#output-caching)

articles/redis/index.yml

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,10 +53,6 @@ landingContent:
5353
url: python-get-started.md
5454
- linkListType: tutorial
5555
links:
56-
- text: Use session state provider
57-
url: aspnet-session-state-provider.md
58-
- text: Use output cache provider
59-
url: aspnet-output-cache-provider.md
6056
- text: Use Redis as a semantic cache
6157
url: tutorial-semantic-cache.md
6258
- text: Use Spring Boot Initializer

articles/redis/overview.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ For more information on how Azure Managed Redis is built, see [Azure Managed Red
2525
2626
Azure Managed Redis can improve the performance and scalability of an application that heavily uses backend data stores. It's able to process large volumes of application requests by keeping frequently accessed data in the server memory, which can be written to and read from quickly.
2727

28-
Redis brings a critical low-latency and high-throughput data storage solution to modern applications. Additionally, Redis is increasingly used for noncaching applications, including data ingestion, deduplication, messaging, [leaderboards](web-app-cache-aside-leaderboard.md), [semantic caching](tutorial-semantic-cache.md), and as a [vector database](overview-vector-similarity.md).
28+
Redis brings a critical low-latency and high-throughput data storage solution to modern applications. Additionally, Redis is increasingly used for noncaching applications, including data ingestion, deduplication, messaging, leaderboards, [semantic caching](tutorial-semantic-cache.md), and as a [vector database](overview-vector-similarity.md).
2929

3030
Azure Managed Redis can be deployed standalone, or deployed along with other Azure app or database services, such as Azure Container Apps, Azure App Service, Azure Functions, Azure SQL, or Azure Cosmos DB.
3131

@@ -35,13 +35,13 @@ Azure Managed Redis improves application performance by supporting common applic
3535

3636
| Pattern | Description |
3737
| ------------ | -------------------------------------------------- |
38-
| [Data cache](web-app-cache-aside-leaderboard.md) | Databases are often too large to load directly into a cache. It's common to use the [cache-aside](/azure/architecture/patterns/cache-aside) pattern to load data into the cache only as needed. When the system makes changes to the data, the system can also update the cache, which is then distributed to other clients. Additionally, the system can set an expiration on data, or use an eviction policy to trigger data updates into the cache.|
39-
| [Content cache](aspnet-output-cache-provider.md) | Many web pages are generated from templates that use static content such as headers, footers, banners. These static items shouldn't change often. Using an in-memory cache provides quick access to static content compared to backend datastores. This pattern reduces processing time and server load, allowing web servers to be more responsive. It can allow you to reduce the number of servers needed to handle loads. Azure Managed Redis provides the Redis Output Cache Provider to support this pattern with ASP.NET.|
40-
| [Session store](aspnet-session-state-provider.md) | This pattern is commonly used with shopping carts and other user history data that a web application might associate with user cookies. Storing too much in a cookie can have a negative effect on performance as the cookie size grows and is passed and validated with every request. A typical solution uses the cookie as a key to query the data in a database. When you use an in-memory cache, like Azure Managed Redis, to associate information with a user is faster than interacting with a full relational database. |
38+
| Data cache | Databases are often too large to load directly into a cache. It's common to use the [cache-aside](/azure/architecture/patterns/cache-aside) pattern to load data into the cache only as needed. When the system makes changes to the data, the system can also update the cache, which is then distributed to other clients. Additionally, the system can set an expiration on data, or use an eviction policy to trigger data updates into the cache.|
39+
| Content cache | Many web pages are generated from templates that use static content such as headers, footers, banners. These static items shouldn't change often. Using an in-memory cache provides quick access to static content compared to backend datastores. This pattern reduces processing time and server load, allowing web servers to be more responsive. It can allow you to reduce the number of servers needed to handle loads. Azure Managed Redis provides the Redis Output Cache Provider to support this pattern with ASP.NET.|
40+
| Session store | This pattern is commonly used with shopping carts and other user history data that a web application might associate with user cookies. Storing too much in a cookie can have a negative effect on performance as the cookie size grows and is passed and validated with every request. A typical solution uses the cookie as a key to query the data in a database. When you use an in-memory cache, like Azure Managed Redis, to associate information with a user is faster than interacting with a full relational database. |
4141
| [Vector similarity search](overview-vector-similarity.md) | A common AI use-case is to generate vector embeddings using a large language model (LLM). These vector embeddings need to be stored in a vector database and then compared to determine similarity. Azure Managed Redis has built-in functionality to both store and compare vector embeddings at high throughputs.|
4242
| [Semantic caching](tutorial-semantic-cache.md) | Using LLMs often introduces a high amount of latency (due to generation time) and cost (due to per token pricing) to an application. Caching can help solve these problems by storing the past output of an LLM so that it can quickly be retrieved again. However, because LLMs use natural language, storage can be difficult for typical caches to handle. Semantic caches like Azure Managed Redis are capable of caching not just a specific query, but the semantic meaning of a query, allowing it to be used much more naturally with LLMs.|
4343
| [Deduplication](https://redis.io/solutions/deduplication/) | Often, you need to determine if an action already happened in a system, such as determining if a username is taken or if a customer was already sent an email. In Azure Managed Redis, bloom filters can rapidly determine duplicates, and prevent problems. |
44-
| [Leaderboards](web-app-cache-aside-leaderboard.md) | Redis offers simple and powerful support for developing leaderboards of all kinds using the [sorted set](https://redis.io/solutions/leaderboards/) data structure. Additionally, using [active geo-replication](how-to-active-geo-replication.md) can allow one leaderboard to be shared globally. |
44+
| Leaderboards | Redis offers simple and powerful support for developing leaderboards of all kinds using the [sorted set](https://redis.io/solutions/leaderboards/) data structure. Additionally, using [active geo-replication](how-to-active-geo-replication.md) can allow one leaderboard to be shared globally. |
4545
| Job and message queuing | Applications often add tasks to a queue when the operations associated with the request take time to execute. Longer running operations are queued to be processed in sequence, often by another server. This method of deferring work is called task queuing. Azure Managed Redis provides a distributed queue to enable this pattern in your application.|
4646
| [PowerBI/Analytics Acceleration](https://techcommunity.microsoft.com/blog/analyticsonazure/how-to-use-redis-as-a-data-source-for-power-bi-with-redis-sql-odbc/3799471) | You can use the Redis ODBC driver to utilize Redis for BI, reporting, and analytics use-cases. Because Redis is typically much faster than relational databases, using Redis in this way can dramatically increase query responsiveness. |
4747
| Distributed transactions | Applications sometimes require a series of commands against a backend data-store to execute as a single atomic operation. All commands must succeed, or all must be rolled back to the initial state. Azure Managed Redis supports executing a batch of commands as a single [transaction](https://redis.io/topics/transactions). |

articles/redis/redis-cache-arm-provision.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,3 @@ $resourceGroupName = Read-Host -Prompt "Enter the resource group name"
160160
Remove-AzResourceGroup -Name $resourceGroupName
161161
Write-Host "Press [ENTER] to continue..."
162162
```
163-
164-
## Related Content
165-
166-
In this tutorial, you learnt how to create an Azure Resource Manager template that deploys an Azure Cache for Redis. To learn how to create an Azure Resource Manager template that deploys an Azure Web App with Azure Cache for Redis, see [Create a Web App plus Azure Cache for Redis using a template](web-app-arm-with-redis-cache-provision.md).

0 commit comments

Comments
 (0)