2 ms·
Committing to geographically dispersed anything is a hard problem. How will apps perform when their front-end is in Virginia and their back-end is in California
by dangrossman 14y ago
Committing to geographically dispersed anything is a hard problem. How will apps perform when their front-end is in Virginia and their back-end is in California? How will fail-over work when it involves moving a 100GB database from Dallas to Washington, instead of between racks in the same building over a private gigabit network?
- goronbjorn 14y agoI agree that it's a difficult problem, but it's Heroku's obligation to solve those problems. You can't position yourself like this: > Heroku takes full responsibility for your app's health, keeping it up and running through thick and thin and not commit to solving hard problems like geographically dispersed EC2 instances. Resource constraints, to be fair, aren't an acceptable excuse at this point. They aren't a floundering startup. They're a part of a multibillion dollar company.