Hey everybody, today let's look upon how one picks one's azure services. There are a lot of services out there and it’s a little complicated don’t you think. Azure is huge, now like over 125 services or something, and it's very difficult to choose the right ones. Here I have some points that will help you to choose the right services. 

Here I am going to discuss about how you choose services in order to run your application in azure, and also for storing your valuable data in Azure. There are obviously a lot more categories like securing your application and things of such kind but let’s just take a sneak peek to this article. 

Running your APP in Azure: 

Some queries you must be able to answer before picking the services; 

1. How much control do I need? 

i.e. do we need control over the load balancers or do I not care? 

2. Where do I need my app to run? 

I.e. is that only in azure public cloud or also on-premises or maybe in other clouds? 

3. what usage model do I need? 

i.e. so, do I need to run my application all the time like a website? Or maybe only it’s needed like every hour or so? 

After answering these big questions, we are able to narrowed down the amount of services that we can pick from. From those services, we can pick the services that actually fits our requirements with the functionality of those services. 

Let’s go to the questions that arose earlier: 

1. How much Control do I Need? 

The question is all about control and responsibility versus the ability to work on business value work on things that actually matter. So, if you look at the categories of cloud computing, those are IaaS (Infrastructure as a Service), PaaS (Platform as a Service), LaaS (Serverless), SaaS (Software as a Service).

For an instance IaaS, you have control over the network and over the antivirus in a Virtual Machine (VM) instance, but you’re also responsible for those things. Also responsible to actually update the antivirus, maybe I need that maybe I don’t. 

 The higher up the stick I get, so for an instance Serverless, I don’t have to worry about scaling anymore, but I don’t have to control over it anymore. It does allow me to work more on the business value, to work on the app itself instead of worrying about the network and the pluming around it. 

One of the ways I like to look at it is that I might enjoy my own car or even building my own car from scratch using a kit, or I might just want to go from point A to Point B and rent a car or a lift, and all the different others ways from public transportation, each one giving me less control or possibly more focus. I can work on business value like writing a book while I’m on the bus ride. 

2. Where do I need my app to run? 

So, obviously, we say it’s Azure, the public cloud but it can mean in Azure public cloud, also it can mean in Azure Stack or hybrids or the on-premises a variant of Azure. There’re lots more types of azure clouds out there with is useable so you can choose according to your preferences and requirements. 

3. what usage model do I need? 

This question is all about how will my app be used? So, if my answer is all the time, like in a website or a web application, it’s always on, it has users all over the world 24/7, then I need to look into services in a classic model. So those are the services that are always on, like a web app for an instance, and you pay for them monthly. If my answer is, I don’t need it all the time but occasionally, let’s say when a new message comes in a queue or every hour, then I need to look into services in the server less or logic as a service category. Those services only run when I need them to, every hour or when and you message is in the queue. I only pay for the execution. 

so, after clearing your doubts on azure and getting answers to the above questions each one of you are able to get some idea to choose the azure services.