Code deploy takes care of deploying the code to all new servers as it boot us on the autoscale group. When you jump all the hoops and get past the issues, the things work relatively well.ĮC2- Compute instances: Used Amazon AMI, installed Apache, PHP and checked out drupal core files, converted to an image.Īutoscaling Group: Launch config & Auto Scaling Group, using the custom image created from EC2ĮLB: Frontend load balancer for web serversĬode Deploy: To deploy the update code files to the web servers. On the plus side, their ARM templates are richer and nicer to use than CloudFormation, however the lack of documentation for them kills all the advantages. Their services labelled Beta are really more like Alpha quality. you now have to have another VMSS just for load balancing/service discovery. You have a VMSS (=Auto Scaling Group) and have a Load Balancer in front of it, your microservice connections fail if the load balancer routes the connection back to the same VM. You have to store your osDisk image in the same storage account as your machine you are running (so you have to pay for your image the full SSD monthly price) You can have SSD's in 128/512/1024GB sizes and you pay for them in full, Spinning disks are billed per actual usage. Default Centos images are 30GB osDisk and you can't resize them, you have to create your own images if you do want to. But the lack of documentation compounds confusion.Īzure has a lot of very weird limitations that don't make any sense: Would be great if you can give some more insights which makes you end up in the conclusion that Azure is not a great choice.ĪWS documentation is excellent, Azure docs are weird and inconsistent and for some bits nonexistent.Īzure API's are inconsistent and weird, but once you figure out they work relatively well. Azure might be expensive (I need to take some time to actually compare the pricing) but i am interested to know why you consider Azure as unreliable.
0 Comments
Leave a Reply. |