Today the LARGEST Public Cloud Provider has had a wide spread outage in the US. Several popular and recognizable websites and cloud services were affected as a result. This seems very familiar to the DYN DDoS attack from October 2016 that took down similar recognizable names as well. What does that mean when it comes to the Public Cloud and the design of your cloud infrastructure?
We have written about this at length ...
Why shouldn’t I Park My Cloud UC / Hosted VoIP System in Google, Amazon AWS, Microsoft Azure? - Part 1
Why shouldn’t I Park My Cloud UC / Hosted VoIP System in Google, Amazon AWS, Microsoft Azure? - Part 2
The point here is understand the REAL story around this and many other points of consideration when selecting your vendors and SaaS solutions. Don't expect that it's all done for you be default. Redundancy cost's extra and it's not automatically included. Also, designing your solution to properly negotiate the redundancy options is not automatic either.
Think hard before you just plug stuff into the cloud and also ASK your upstream vendors what their game plan is if they are utilizing public cloud for their deployments.
Here at BVoIP we use multiple SaaS solutions in our day-to-day world but our core offering is in a dedicate private cloud environment for multiple reasons. One of those reasons being that we are driving on our Dedicated Private Servers and not on the Public Cloud for the mainstay of our offering.
We understand that at some point or another things "break" so it's worth noting that most things in the tech arena come to Planning, Time, and Money in the end.