Virtual Machines (VMs) are available on Microsoft Azure, providing what is built as a low-cost, per-second compute service, available via Windows or Linux.
$0
Per Hour
Oracle VM VirtualBox
Score 9.3 out of 10
N/A
Open source, cross-platform, virtualization software that enables developers to deliver code faster by running multiple operating systems on a single device, used to deploy applications on-premises and to the cloud. Oracle VM VIrtualBox is Oracle's cross-platform virtualization offering, acquired with Sun Microsystems in early 2010. The software was originally developed by Innotek GmbH.
If you want to host a dedicated Windows server on the cloud, and especially if you want to integrate it with your on premises Active Directory, Azure Virtual Machines should be your first choice. Obviously running Linux on Azure works very well too, but given Azure's pricing is not the cheapest, there are other providers out there that have a better cost-benefit ratio for Linux. That said, hosting Windows on Azure can be affordable (especially when compared to other providers) if you plan your licensing, topology, and application architecture correctly.
It is best suited when you want to have different operating systems on your laptop or desktop. You can easily switch between operating systems without the need to uninstall one. In another scenario, if you expect some application to damage your device, it would be best to run the application on the VM such that the damage can only be done to the virtual machine. It is less appropriate when time synchronization is very important. At times the VMs run their own times differently from the host time and this may cause some losses if what you doing is critical. Another important thing to take note of is the licensing of the application you want to run your VM. Some licenses do not allow the applications to be run on virtual servers so it is not appropriate to use the VM at this time.
When demand is high, we scale the service out, eg During a Football Match.
When a football match is over and the throughput of data from OPTA drops we save by the service scaling back in.
Our App Service Plans along with the Clean C# code are lightening fast giving a good customer experience.
When producing the TV Guide information and a program overruns its scheduled time, a client can instantly be updated to the new programming schedule as our change is instant and its in the right place for all the clients to download and adjust their television guides appropriately to send out to the public giving a 24x7 uptime service that is precise and accurate and resilient to outages due to failover zones around the world.
Pricing can be a concern if you are truly agnostic to which cloud you are building your particular solution in.
The UI, as is the case with any cloud provider, is crowded.
As with any cloud provider, it can be difficult to tune in exactly the right amount of servers for your needs...you might find yourself under/overprovisioning.
I have had issues in the past when it has come to resizing VM disk storage. The issue is entirely detailed here: https://www.virtualbox.org/ticket/9103 -- the problem was caused because of having existing snapshots (which error message output was not detailing). I haven't had to deal with the issue due to my dynamic disk sizes not being small from the start anymore (this is mostly an issue for my Windows VMs where the base disk may need significant size for the OS). It looks like, for a resize, that a merge of all snapshots has to occur first -- one user on that list details a workaround to maintain snapshots by cloning the VM. (Note: 5.2 was just released a few weeks ago, and looks like it should prevent the problem happening in the future by properly informing users that it isn't possible with snapshots).
Certain scenarios, like resizing disks, required dropping into a terminal as there were no options to previously do so via the GUI. According to some recent posts, I've seen that v5.2 has added disk management stuff like that to the GUI (or will be adding it). I'm comfortable with dropping into the terminal, but in a teaching scenario or when evaluating the learnability of the tools, it complicates things.
Easy and quick to use. Runs at sufficient speed even with 5/6 VMs running, and can handle a bridged network with ease. Easy to disassociate from the host to ensure the environment built within VB is quarantined should anything happen, meaning no risk to physical hardware. Quick to pick up. Quick to add new machines. Cloning feature very quick and comprehensive. I've never had a VM crash or freeze.
I give the overall support for Azure Virtual Machines a 7 because I think while the overall support do a great job there are still areas that it could improve on such as efficiency and speed. So while I only give it a 7 and it has some issues it is still better than the overall support at Amazon EC2 Auto Scaling.
Azure Virtual Machines offer unparalleled flexibility in provisioning, managing and upgrading the VM instances, both manually and programmatically. AVM offer very granular billing options and enables high costs optimisations (while still being costly). The other competitors I mentioned are very good at offering dead-cheap VMs. But if you need anything beyond that, especially for big computing, you need Azure Virtual Machines.
VirutalBox is very similar to using Vmware with the slight difference in appearance and what might be considered a less polished look. However, what it lacks in polish and looks it makes up for in functionality, easy of use and the wide range of operating systems and features it supports without the need of buying the full professional edition
The only problem I have found is that the deployment is dependent and intrinsically linked to the Host OS. This is different from bare metal solutions which remove that dependency on a Host OS. The latter is more reliable and removes a layer of potential failure.
It's so easy to spin up new instances, that it becomes also to easy to have to many of them to manage. Many teams end up with a couple of hundreds of VMs after a short while, making the whole thing very hard to maneuver
Azure VMs are the next step for us to rely on Onprem servers, and leaving the management of the infrastructure to the professionals
The ease of use, is also important when our main focus is to deliver new applications and integrations fast, and not having to worry about infrastructure. We sell bottles, not CPUs
For personal use, there is no monetary investment, I am running 5 CentOS servers flawlessly in my home lab.
Saves a ton of money in an enterprise environment by not having to purchase physical test servers. (Cost of Enterprise product is way lower vs Cost of standing up physical servers and/or cloud servers)
Makes virtualization very easy and friendly for everyone for test instances.
