Google's Transition from Single Datacenter, to Failover, to a Native Multihomed Architecture - High Scalability -
highscalability.com/blog/2016/2/23/googles-transition-from-single-datacenter-to-failover-to-a-n.html
From the page
Saved with the link. Notes from 2007 to 2016 are mostly the page's own words, so this is probably an excerpt.
Making a system work in one datacenter is hard. Now imagine you move to two datacenters. Now imagine you need to support multiple geographically distributed datacenters. That’s the journey described in another excellent and thought provoking paper from Google: High-Availability at Massive Scale: Building Google’s Data Infrastructure for Ads.
Same host · 17 links from highscalability.com
- 10 Tips for Optimizing NGINX and PHP-fpm for High Traffic Sites
- How Google Invented an Amazing Datacenter Network Only They Could Create
- A 360 Degree View of the Entire Netflix Stack - High Scalability -
- The QuickBooks Platform - High Scalability -
- The Always On Architecture - Moving Beyond Legacy Disaster Recovery - High Scalability -
Saved the same week · 24 links that week
- IBM Launches Bluemix OpenWhisk, an Event-driven Programming Service - The New Stack
- Analyst Watch: Water-Scrum-fall is the reality of agile
- claudiajs/claudia: deploy Node.js microservices to AWS easily
- LogicMonitor Integrates With PagerDuty to Automate Incident Workflow
- Using Amazon API Gateway with microservices deployed on Amazon ECS