3 ms·

There are a few issues, but to be fair I've encountered similar things in all the cloud and VPS hosting services I've used. However, I do remember that I was on

There are a few issues, but to be fair I've encountered similar things in all the cloud and VPS hosting services I've used. However, I do remember that I was once trying to push Azure as a solution and they promptly had an outage. We went with AWS instead. It's not that AWS don't have outages, they do, just that the timing was really bad. Also, don't use the preview services in Azure apart from to try them out. They really are previews. I've recently written a three part series of blog posts on AWS vs Azure. The third part, on pricing, is out today. https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-3 https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-c... Edit: One plus of Azure (at least for me) is that it runs on renewable energy. https://www.microsoft.com/about/csr/environment/renewable_energy https://www.microsoft.com/about/csr/environment/renewable_en...

jnsaff2 10y ago
To illustrate the "don't use previews" point, they recently announced VNet peering where two VNets could be peered together without VPN gateways. We started using them and at some point discovered that half of our instances in a VMSS could not talk to the other VNet and half could. We were tearing our hair out, there is absolutely no configuration difference between those hosts. We did contact their support and after a few days they came back with this: "there is a small bug with the peering that we are aware of, only hosts which were launched before peering was set up can communicate with the other VNet, for new hosts to communicate you need to delete the VNets, just recreating the peering is not enough" They did offer to add our hosts in by hand, but we were running back to VPN Gateways .. ... which also have a peculiar problem, the Standard level GW's are capped to 100Mbps but burst to 200Mbps and then get throttled to 0 for about 20 seconds or so. This was also confirmed by Support. Our experience with Azure has been very painful, things look good on paper but it's pretty much lies or illusions.

jnsaff2 10y ago

To illustrate the "don't use previews" point, they recently announced VNet peering where two VNets could be peered together without VPN gateways. We started using them and at some point discovered that half of our instances in a VMSS could not talk to the other VNet and half could. We were tearing our hair out, there is absolutely no configuration difference between those hosts. We did contact their support and after a few days they came back with this: "there is a small bug with the peering that we are aware of, only hosts which were launched before peering was set up can communicate with the other VNet, for new hosts to communicate you need to delete the VNets, just recreating the peering is not enough" They did offer to add our hosts in by hand, but we were running back to VPN Gateways .. ... which also have a peculiar problem, the Standard level GW's are capped to 100Mbps but burst to 200Mbps and then get throttled to 0 for about 20 seconds or so. This was also confirmed by Support. Our experience with Azure has been very painful, things look good on paper but it's pretty much lies or illusions.