Starter for 10: Meet Jonna Iljin, Nordcloud’s Head of Design
When people start working with Nordcloud, they generally comment on 2 things. First, how friendly and knowledgeable everyone is. Second,...
Azure App Services is arguably the most popular Azure PaaS service, allowing you to host Web Sites and App Functions in a fully managed service.
Once you had created your App Service Plan, and Web App, API App, Logic App or Function you can upload your code and have a simple website, API, Logic App or Function up and running in under 10 minutes. Of course, there are a number of other configuration options, such as binding a domain name, adding an SSL Certificate and the ‘out the box’ ability to do blue / green deployments. However, it was simple to get up and running and like any PaaS, Service should be, simple to manage.
Azure App Servers runs in a multi-tenanted Environment. In short, your App Service shares the same hardware as other Azure Customers, and while this provided a cost-effective hosting solution, the multi-tenanted aspect introduced a number of restrictions around scalability and security. To address this, in June 2015, Microsoft Azure released App Service Environments (ASE), a premium tier of Azure App Services, which allow you to run App Services isolated within a subnet of your own Virtual Network.
As a premium service, ASE comes with a premium price tag, so if you are architecting a solution that included an ASE, (compared to the multi-tenanted and cheaper equivalent) you have to make sure your business case can justify it. If you need:
– Your App Service to connect to infrastructure within your local network, via a site-to-site VPN, Express Route of VNET Peering,
– Your App Server hosts internal or Line of Business Application that should not be publicly accessible,
– Layer 3 Network Access Control, on both inbound and outbound traffic,
– A Static Outbound IP Addresses that can be whitelisted on on-premises or third-party firewalls, including securing connections to AzureSQL,
– You need more compute resource (without an ASE, you have can have a maximum of 10 compute resources, with an ASE you can have up to 100),
– You wish to place a Network Virtual Appliance in front of your App Service, or,
– You require a fully isolated & dedicated compute resource,
In July Microsoft released the next generation ASE: App Service Environment Isolated or ASEv2, but what are the differences between ASE Isolated and the Original (ASEv1) and should you migrate?
If you are used to deploying ASEv1, the biggest change you will notice is that they have made using an ASE simpler, and there is less to set up and manage. It feels a lot more ‘PaaS’ like and is generally a good experience. Gone is the configuration overhead of ‘Front End Workers’ and ‘Backend Workers’, and you no longer need to worry about ensuring you have additional workers for fault-tolerance and scaling – this is all now managed for you.
This change means that there is a large change to how an ASE is priced. There are two components you need to be familiar with to be able to price an ASEv2:
ASEv2 only supports the ‘I’ series of virtual machines – these are all Dv2 based machines, which means faster cores, SSD storage and twice the memory per core when you compare to ASEv1. In short – the Dv2 almost doubles the performance compared to the previous generation.
As part of the process of making ASEv2 simpler, fault tolerance is now managed for you. You no longer need to have, or pay for, standby workers.
In ASEv2, they have simplified how the scaling works to bring it inline with you auto-scale your App Service Plan outside of an ASE. You no longer need to worry about ensuring you have enough workers at the ASE level to enable your scaling actions to happen, and again, means you are not paying for computer resource that you’re not using.
If you do a head to head cost comparison of ASEv1 and ASEv2, you might question if ASEv2 is any cheaper. However, when you consider that you are getting almost twice the compute power in the ‘I’ series of computer resource (and therefore should need less of them) and that you no longer need to pay for fault-tolerance or workers ready to scale, ASEv2 will work out cheaper.
Microsoft Azure has taken the end user feedback and each of the changes we have listed above bring real benefits. Nordcloud has already seamlessly migrated a number of its clients from ASEv1 to ASEv2 and they are already benefiting from the cost savings, both directly and indirectly from the reduced effort of operating the ASE.
If you would like to talk to Nordcloud about if an ASE is suitable for your requirements, or how we can help quickly and seamlessly migrate you from an ASEv1 to and ASEv2, please get in touch today.
Let’s discuss how we can help with your cloud journey. Our experts are standing by to talk about your migration, modernisation, development and skills challenges.