Microsoft Azure: SLA for single servers
Relatively recently, in early August, I wrote that Microsoft is constantly working to improve the reliability of virtual machines in Azure.
The other day there was news that the next, most important step in this direction has been made. Microsoft finally introduces SLA for single virtual machines using Premium Data Warehouse.
Some details under the cut.
The topic of SLA for single machines is one of the main problems when communicating with the customer on the topic of migration to the cloud. This is not only characteristic of Microsoft Azure. Exactly the same story with AWS . Cloud providers tell you - “Use cloud-ready applications and scaling out. We easily guarantee you an SLA for sets of several machines, if you designate for us that they are used by the same service, so that we spread them to different equipment. ”The position is very clear and reasonable. However, not all applications provide such an opportunity (let us leave aside the discussions that applications with outdated architecture are bad and you should get rid of them anyway), and, in general, the customer is very nervous about the news about that its single virtual machines will not have a guaranteed SLA.
The November Azure Update provides this kind of SLA. However, with the proviso that this, for the moment, concerns only virtual machines all disks of which lie in the Premium storage (an interesting way to promote this more expensive storage).
The official SLA on the Azure portal has already been updated to version 1.3 in line with this news.
')
Once I waited for the news about the introduction of SLA for single machines with Premium disks, now it remains only to wait for similar news (albeit with the worst SLA) for machines with disks on standard storages.
NB It is important to note that SLA means Microsoft’s willingness to return some of the funds you pay for the services you are using, and not to compensate you for the losses incurred due to downtime.
The other day there was news that the next, most important step in this direction has been made. Microsoft finally introduces SLA for single virtual machines using Premium Data Warehouse.
Today, we are announcing a new 99.9% single-instance availability of single VMs.
Some details under the cut.
The topic of SLA for single machines is one of the main problems when communicating with the customer on the topic of migration to the cloud. This is not only characteristic of Microsoft Azure. Exactly the same story with AWS . Cloud providers tell you - “Use cloud-ready applications and scaling out. We easily guarantee you an SLA for sets of several machines, if you designate for us that they are used by the same service, so that we spread them to different equipment. ”The position is very clear and reasonable. However, not all applications provide such an opportunity (let us leave aside the discussions that applications with outdated architecture are bad and you should get rid of them anyway), and, in general, the customer is very nervous about the news about that its single virtual machines will not have a guaranteed SLA.
The November Azure Update provides this kind of SLA. However, with the proviso that this, for the moment, concerns only virtual machines all disks of which lie in the Premium storage (an interesting way to promote this more expensive storage).
VMs must be using premium storage
The official SLA on the Azure portal has already been updated to version 1.3 in line with this news.
')
Once I waited for the news about the introduction of SLA for single machines with Premium disks, now it remains only to wait for similar news (albeit with the worst SLA) for machines with disks on standard storages.
NB It is important to note that SLA means Microsoft’s willingness to return some of the funds you pay for the services you are using, and not to compensate you for the losses incurred due to downtime.
Source: https://habr.com/ru/post/315880/
All Articles