11–20 of 136 posts
My main concern with picking GCP would be that Google has a history of shutting down projects. I feel like they are more likely to shutter GCP than Amazon is with AWS.
It totally wrote off Azure (2nd in market size) because its a "Linux second" cloud (what does that even mean in a virtualized world).
Also, you forgot to analyze support and SLAs around functionality. Good luck with GCP when something goes wrong or they decide to sunset a feature.
Earlier quoted context omitted.
Yes http://www.alexa.com/siteinfo/quizlet.com
On the other hand, https://www.quantcast.com/quizlet.com
The Best Cloud is probably a combination of all. Since that would give you the highest Availability.
In a similar vein: http://journalofcloudcomputing.springeropen.com/articles/10....
https://labs.spotify.com/2016/03/10/spotifys-event-delivery-...
This should really be titled "A comparison of AWS and GCP." It totally wrote off Azure (2nd in market size) because its a "Linux second" cloud (what does that even mean in a virtualized world). Also, you forgot to analyze support and SLAs around functionality. Good luck with GCP when something goes wrong or they decide to sunset a feature.
One of the reasons why Spotify went with Google Cloud is because of their superior support.
Interesting read. Can someone explain this point to me? "Software-defined networking means that google.com appears to be one hop away" One hop from...? Everywhere? Each server? How does that help? I understand 'traceroute' but not where that single hop to Google comes in and why that's great.