Azure services - what are the actual use cases?

Asked

Viewed 157 times

2

I don’t know if this question is in Sopt’s scope, in case I’m not asking you to tell me to delete it or tell me how to improve it. I am developing Restful services with ASP.NET Webapi and single-page applications and I searched Windows Azure is a good option to put all this on the internet.

The only problem is that I do not understand how to choose what to hire there on the site. I researched a lot and could not find out, so I decided to ask. Basically, when I access the price calculator I have these options

inserir a descrição da imagem aqui

But the problem is, I get a little confused about which option to use. I know you can compose yourself with options of more than one category, but the price ends up being absurd, so I guess it’s not like that.

In a way, what I’m doing fits into websites. Searching more on the Azure site I found this on the sites option:

Host websites, web Apis, real-time apps, and mobile apps.

But at the same time, it seems to fit into cloud services, which says

Cloud Services enable you to execute application code in the cloud by deploying web and work functions, with Azure taking care of deployment details.

But at the same time, I need a database, so it fits into data management.

I’m starting now in Zure and I don’t know how this "pay for what to use" thing works, because everything separated so I’m kind of in doubt what should be chosen.

In this case, what are the actual use cases of each of these categories and which of them fits API’s Restful, SPA’s and etc?

windows-azure

1 answer

2

The answer is that you can host both cloud services (web role) and web sites. There are some Features that only work in cloud services ex:

-vpn for your business network, for example.

Another cool cloud service thing. You have two environments (staging / Production), that is, you can publish a new version of the api in staging, and after homologated, "turn the key" to production. Since Deployment will already be in the Azure datacenter, it is simpler and faster to publish the same version in Production.

Obviously there is a small variation in cost.

In short I think this is it, the two options add you.

  • Thank you for the reply @Thiagocustodio. And for example, if the application is small and doesn’t need a lot of resources at first I can start by putting it on web sites and then migrate without difficulty to cloud services?

  • It depends on what you judge as "without difficulties". A new publication would be necessary. The domain would also be changed from ".azurewebsites.net" to ".cloudapp.net". If you’re going to expose an api to customers, this could be a problem.

Browser other questions tagged windows-azure

You are not signed in. Login or sign up in order to post.