In this multi post series we are going to be building a git-based headless CMS. We will be using Jekyll to build our website, GitHub actions for building a continuous delivery pipeline that will deploy our website to Azure. We will leverage the infinite scalability of Azure storage account’s blob storage along with Azure CDN to reduce the load time for our users around the world.
In this post we are going to be looking at how to build a consumption-based task execution framework that can scale elastically as demand rises and falls.
Azure resources can be broadly divided into the following categories:
In an ideal world, all our workloads will be entirely consumption based and we only pay for what we use. Often that is not the case our workloads consist of a mix of consumption-based PaaS, hour-based PaaS and sometimes sprinkled with IaaS for good measure. One of the major downsides of the hour-based PaaS is that they do not have a “stop” or a “start” button like IaaS resources generally do. In this post we are going to be looking at how we can save more than just a few bucks on our Azure bill by turning off the hour-based PaaS services when we are not using them.