Public cloud is not infinite (if you ever thought it really is…)

I’m working on some heavy lab tests in these weeks, plus I’m travelling a bit more than usual, so my blogging activity has slowed down a bit. As I’m catching up on the news I read around, I found two different articles that can give to all of us a good perception about two things about the public cloud, or the so called “hyper-scalers”. They have insanely massive resources, but as insane as they are, they are not infinite.

Cloud outages and the couch architects all over the world

Last week, another outage of a large cloud provider hit the news, and the many companies using their services were impacted. This time it was Amazon Web Services, as their S3 service in the US-East region has been down for almost 4 hours, impacting so many other cloud services that are relying on this object storage technology. What impacted me, however, had been the reactions of other IT people around and the couch architects all over the world.

Load balancing services with AWS Route53 DNS health checks

DNS is a great technology that everyone uses over internet. How would you reach a given website if you weren’t able to solve its name to the IP address? Would you memorize the public IP addresses of any website you want to reach? No, and with IPv6 coming in the future, DNS will become even more important for internet consumption. But DNS has one drawback: its records are usually static, and if a platform is dynamic and spawn/removes instances on the fly, it needs to have a way to modify the DNS records that are published, so that a non-reachable instances is not even listed.