Azure stories. Create App Service

Lately I was talking about difference in PaaS and IaaS. I will probably come back to IaaS in the future, but most of the time I'll concentrate on PaaS solutions. PaaS is much closer to mine mindset, it's more intuitive for developer. I don't want to know (mostly) what's inside PaaS, what's under the hood, I just want it to work.
I want to create to very simple pages both displaying only Hello World, based on .Net and Java.
First the code and deployment packages. You can find full explanation here, and we can assume that we have 'something' ready to be deployed.
Where I can deploy it?


App Service. It's very nice intro here. App Service is basically platform for running web sites, APIs mobile apps or logic apps (loosely coupled functions). I'm interested for this moment in Web App - fully managed compute platform that is optimized for hosting web sites and web applications.

Let's go to Azure portal.
Of course to work with Azure you need to have some Azure credits. I have mine from MSDN subscription (150$/month for education purpose), you can get yours also from Dev-Essentials, Microsoft Imagine formerly DreamSpark, or trial version (or just buy some credits).

Creating is very easy just click green plus sign, find service that you want and create. Of course there will be a lot of questions asked in the way.
For creating AppService you need to create some additional resources or choose existing. I will create new ones, starting with Resource Group

First I create App Service based on Tomcat 8. After creating web site is ready to use (you need to wait for it a little because it's 'cold starting' - I deleted the waiting time form presentation).


Second Web App I've created from resource group overview blade. To have both applications in the same resource and App Service Plan (with the same pricing tier).



Comments

Post a Comment

Popular posts from this blog

Azure post deployment scripts

Image
Let's do a trick. After deploying application (that was easy with Ftp or Git ) it would be nice to take some action. For example send an email, or write release notes to release page. I will do much fancier thing - I will write some text to console output.
Read more

Mobile view lifecycle. Fixing Xamarin.Forms Page lifecycle

Image
For mobile applications the highest priority is user. What user can see and interacts with. Application should react not only on user interacting with it but also user interacting with operating system. That's why not only application has it's own lifecycle but also "view" has it's own lifecycle. In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is being suspended and reactivated. View know quite a lot about outside world and view lifecycle is very similar to application lifecycle. Compare below first application and then view lifecycle diagrams: In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is
Read more

Mobile application life-cycle Android vs iOS vs Xamarin.Forms

Image
Lifecycle. One of the most common recruitment questions. No matter what technology you work with this is something that should be well known and understood. It's good to know how application behaves, what it is allowed depending on its state and when to react on specific lifecycle events. In mobile world lifecycle is even more complicated because there is no 1 answer but 3 in this case: Android. iOS. Xamarin.Forms. I use also Xamarin.iOS event names in my diagrams, but the sequence is the same. Lifecycle is the definition when your application have access to resources and when react on state change. For mobile the biggest priority is what user can see and interacts with, so active application have priority in using system resources. System has limited pool of resources, so  applications running in background (not visible to user) is limited by system in how much resources can it use and also system decides when application needs to release all resources (be closed/killed/end o
Read more