Skip to main content
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.

  1. Consumption
  2. 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

Popular posts from this blog

Glimpse - Key Vault Vs App Configuration for App service In this post, we are jsut going to see glimpse of comparison between Keyvaukt and App Configuration for App services references. Why we are comparing these two? Recently App Configuration references on App Service become Generally Available and it can complements Keyvault. Let us consider a scenario that we need to have client-id and secret which will be used in an API call for authentication from Azure function app/ App service / Logic App standard, in a secure place. So, Here we come to know 2 azure native services are as follows Azure Keyvault Azure App Configuration Azure people(we) typically use keyvault to handle secrets in secure way whereas App Configuration also complements Azure Keyvault then which is better or in which scenario we can pick either of the one. According to me, We can go for keyvault when we need to handle secrets environment specific. Here, enviro...
Post a Comment
Read more
Glimpse - Azure function migration from .net6 in-process to .net8 isolated Microsoft/Azure periodically announces the end of support for some services and ask us to migrate to a new version/release when they come up with a robust solution than the deprecated. In this post we are going to see a glimpse/UI configuration change of azure function 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗳𝗿𝗼𝗺 .𝗻𝗲𝘁𝟲 𝗶𝗻-𝗽𝗿𝗼𝗰𝗲𝘀𝘀 𝗺𝗼𝗱𝗲𝗹 𝘁𝗼 .𝗻𝗲𝘁𝟴 𝗶𝘀𝗼𝗹𝗮𝘁𝗲𝗱. Here, I'm not going to deep dive about the migration whereas going to see the illustration of changing .net version from UI. For learning, GUI is the best place to start. So, as a dev guy we would prefer azure portal mostly. Consider a scenario that, you're requested to migrate your existing .net6 function app to be migrated .net8 isolated, you would go to settings panel and try to change the version in configuration, but the option would be disabled, it was disabled for me initially. Shocking and Afraid! After some point of ...
Post a Comment
Read more
𝗚𝗹𝗶𝗺𝗽𝘀𝗲 - 𝗔𝘇𝘂𝗿𝗲 𝗱𝗶𝘀𝗸 𝘂𝘀𝗲 𝗰𝗮𝘀𝗲𝘀 Hi Present days, Container based services/applications are growing than applications running from virtual machines. Even though container services evolving IT apps landscape, we could not boycott VM usage. Azure VM also requires and plays vital role for some scenarios. In this post, we are going to see just glimpse of azure disks of VM. This post is not about standard vs premium disk use case FYI. Azure VM can run with OS disk but it is not good practice. There are three types of disks. OS disk Data disk Ephemeral disk We need to know when to use what then only we can avoid performance bottleneck. 𝗗𝗮𝘁𝗮 𝗗𝗶𝘀𝗸 - If we install applications as well in OS disk, we could face performance issue. It is best to use OS disk to have OS infos and booting. The benefilt of Data disk is Easy maintanence Backup and disaster recovery Performance isolation (as it is far from OS acti...
Post a Comment
Read more