Skip to content

Commit 85373b3

Browse files
authored
Changes to scenario, event driven scaling sections
Made few changes to include common function scenario in scenario section. Also, included Cosmos DB as part of Event driven scaling section.
1 parent ae3b2b2 commit 85373b3

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

articles/container-apps/functions-overview.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,22 +37,27 @@ Azure Functions on Container Apps provide a versatile combination of services to
3737

3838
- **Serverless workloads**: Serverless workload processing of videos, images, transcripts, or any other processing intensive tasks that required GPU compute resources.
3939

40+
- **Common Azure Functions scenario**: In general, all common Azure Functions scenarios like processing file uploads, running scheduled tasks, responding to database changes, machine learning/AI and others mentioned [here](/azure/azure-functions/functions-scenarios?pivots=programming-language-csharp).
41+
4042
## Event-driven scaling
4143

4244
All Functions triggers are available in your containerized Functions app. However, only the following triggers can dynamically scale (from zero instances) based on received events when running in a Container Apps environment:
4345

4446
- Azure Event Grid
4547
- Azure Event Hubs
46-
- Azure Blob Storage (event-based)
48+
- Azure Blob Storage (Event Grid based)
4749
- Azure Queue Storage
4850
- Azure Service Bus
4951
- Durable Functions (MSSQL storage provider)
5052
- HTTP
5153
- Kafka
5254
- Timer
55+
- Azure Cosmos DB
5356

5457
Azure Functions on Container Apps are designed to configure the scale parameters and rules as per the event target. You don't need to worry about configuring the KEDA scaled objects. You can still set minimum and maximum replica count when creating or modifying your function app.
5558

59+
Auto scaling for Azure Cosmos DB trigger and Durable functions is currently supported using connection strings only. Managed identity support will be available soon.
60+
5661
You can write your function code in any [language stack supported](/azure/azure-functions/supported-languages?tabs=isolated-process%2Cv4&pivots=programming-language-csharp) by Azure Functions. You can use the same Functions triggers and bindings with event-driven scaling.
5762

5863
## Managed identity authorization

0 commit comments

Comments
 (0)