Skip to main content

Azure Virtual Machines (Day 15 of 31)

List of all posts from this series: http://vunvulearadu.blogspot.ro/2014/11/azure-blog-post-marathon-is-ready-to.html

Short Description 
On Microsoft Azure you have the ability to run, manage and use your own Virtual Machine. In this case you have full control to the OS and different configuration at that level. The hardware virtualization give you the possibility to install and run any kind of OS from Windows to different Linux distributions.


Main Features 
Not only Windows OS
Even if we are talking about a cloud solution from Microsoft, we have the ability to run different Linux distributions like Ubuntu or Suse. On top of this there are also other OS that can be used like Openlogic.
Custom VM Image
You have the ability to create your own Virtual Machine image and upload it. The custom image can contains not only the OS, but also the software that you need for your use case.
Scaling
There is support for scaling from 1 or 2 VM to 500 or event 1000 Virtual Machines.
Per Minute billing
Because money are very important, the billing is per minute and not per hours. In this way you will pay only what you use, nothings more.
Load Balancing
There is an out of the box load balancer in front of Virtual Machine that can be used with success to distribute the load cross multiple virtual machines.
Intensive I/O Storage
With the new storage, based on SSDs, you can have a minimum latency (less than 1 millisecond) with 50.000 IOPS.
Large storage
The current infrastructure give us the possibility to have disks that can have in total 32TB of storage.
Pre-Configured VM Images
When you create a VM, you have the ability to use a pre-configured VM, where SharePoint, Oracle, SQLServer, Visual Studio is already installed.
Pay OS or software license on the fly
There are images with different configuration that allow you to use them without having the license of the software that is installed on them. This is possible because the cost of the software license is included in per minute billing.
Auto Scale
There are different ways to scale up or down automatically. For example you ca configure to scale up based on CPU level or at a specific time. Of course the scaling is not only in one way and you can configure rules that allow you to scale also down.
PowerShell 
Because usually ITPros are responsible for Virtual Machine and the infrastructure, the configuration and management API is not only exposed as REST API, but it is also exposed as PowerShell commands.
Disaster Recovery Plan
All the content of VM is replicated automatically in a second data center from the same geographical region. In this way if something happens with the first data center the content is available on the second one.
Different tiers
There is a wide range of tiers configurations that can be used for Virtual Machines. From the small one to the one that are CPU intensive or memory intensive. Because of this you can start from 768MB of memory and go to 112GB of memory and 32 CPU cores.
Run the same image on Azure or on-premises
The same image can be run on Azure or on-premises. You even have the possibility to migrate an existing VM image from one environment to the other one.  

Limitations 
Custom images configuration 
When you need to create your own custom image with different configuration, you will need to manually create an image where you install all the software that you need.

Applicable Use Cases 
Below you can find 3 use cases when I would use VMs.
Migration to cloud
For existing legacy system, there is the possibility to migrate the existing VM to Azure without having to change the software that runs on them. In this way you can reduce the hosting costs and scale more easily without having to rewrite your systems.
Run custom software
If you have custom software to run, than Azure VMs can be the perfect solution for you. You can run a wide variety of OS and configurations on them.
Optimize Cost
If you need VM only for a limited time period, than this may be a good solution for you. When you don’t need to run VMs, you can keep only the image of them on Azure Storage and use it only when you need it.

Code Sample 
-

Pros and Cons 
Pros

  • Scalable
  • PowerShell support
  • Linux and Oracle support
  • Different hardware configuration based on you needs
  • Auto-Scale

Cons
-

Pricing
When you are calculating  the costs of VM you should take into account:

  • Number of VMs and there configuration
  • Storage size
  • Outbound traffic
  • Licensing cost


Conclusion
Azure VMs are a great solution when you need a place to run and manage your own Virtual Machine.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP