Azure Logic app - When to choose which plan (Consumption vs Standard)?
#cloud #azure
Hi All!
When we want to perform some workloads without worry about an environment in our hand and need serverless architecture (i.e Microsoft Managed), we can go for either Azure function App or Logic App.
In both of Logic App and Function App, we need not to worry about the infrastructure. Microsoft will take care of it at that time of workload(s) running. i.e. for example, If we choose Azure function app .NET based, MS will take care of OS and its necessary packages installation to run etc..,
One who likes code part can go for Function app and Some who likes visual designer to create flow/connectors can go for Logic App.
In this article we will see which plan type we have to choose for our workloads.
Azure Logic App service provides a way to automate workflow (i.e Workflow is a series of steps that defines a task, business process, or workload).
We need to pay attention carefully while create a Logic app. If not, either we may loss money or halt in the middle due to not able to achieve some feature because of limitation(s).
For example, If I create a Logic app in standard plan where it enough and should have with consumption because it runs occassionally, we need to pay from the beginning (not even for running).
Logic App has 2 set of plans as below.
- Consumption
- Standard
Go for Consumption when your workload(s) come under the below category
- Pay per run - i.e. Cost calculated only/whenever workload running.
- Multi-Tenant/Shared - Logic App can be accessed by other tenants including home tenant.
- Entry-level, ad-hoc - It will be suited for R&D, small adhoc workflows running with limited use.
- Only one workflow supported - You can't create multiple workflows in single Logic App.
- When you don't want Virtual Network Integration, Private Endpoint support, Network Isolation
- Need not of Hosting plan.
Go for Standard when your workload(s) come under the below category
- Single-Tenant- Logic can be accessed only by home tenant
- Cost calculated from the created time wven though workflow not run, need to pay.
- It suits for Enterprise level
- Multiple workflow - You can create multiple workflows in single Logic App. (i.e 1-to-Many relationship is possible)
- When you need Virtual Network Integration, Private Endpoint support, Network Isolation
- Require Hosting plan - Hosting plan is a storage mechanism which stores state, run history, artifacts of workflow for Logic app ,either azure storage or (SQL(preview) and Azure storage)
Comments
Post a Comment