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.
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.
Netflix decided in 2008 that its new business model would have been the complete consumption of public cloud, specifically AWS. It took 8 years to the leader in Video Streaming to complete the migration of its services into AWS, and now Netflix doesn’t run any significant workload in its own premises.
Latest news about telecommunication companies and their struggles against giant cloud service providers show how the war for the public cloud is at its peak, and we are starting to see the first victims.
Looking at the latest announcements and the history of the behemoth of public cloud services, probably yes. And a leading one.
Since I started to write my first articles about VMware vCloud Hybrid Service, I received some emails from people asking me if those articles where well suited with my daily job. For those who do not know, I work in Switzerland in a vCloud Service Provider, so maybe these two things were felt as in […]