Any calculations we make here are theoretical and the best way to learn the real behavior and the scale needs of your application is through performing load testing and by monitoring and analyzing production. For the initial budgeting purposes, however, we need to make assumptions that will allow us to estimate the ballpark costs.
First, let's take a look at each one of the services used in our application, looking at pricing as a function of load perspective. This gives us an overall sense of what each component of the application will cost and a sense of whether or not it is cost-effective in an overall architecture. For instance, if the Logic App becomes the costliest component of the application, maybe it is best to move its functionality into Azure Functions and pay the price of custom code development once, rather than paying...
