4 ms·
This depends a lot on your software design. You have to shed a lot of assumptions before you can even begin to consider redundancy. If your software can only
by dlsspy 17y ago
This depends a lot on your software design. You have to shed a lot of assumptions before you can even begin to consider redundancy. If your software can only run on one computer, then nothing much matters.
It would be a worthwhile experiment to see what it'd take to get your site running on GAE or perhaps heroku. In both cases, you are sufficiently constrained such that front-end scalability is trivial, and backend redundancy is managed for you.
Of course, many of us have done this ourselves, but these days I'd rather just get it in a box where I'm doing something fairly small (i.e. could even run on one computer).
- oomkiller 17y agoThe issue with heroku and/or GAE is that they are single services. They have and will continue to have unplanned downtime. The issue here is mitigating a single service's downtime by having redundancy. Redundancy almost always involves duplication of resources. Essentially, you could switch to GAE or Heroku, but you haven't gained much, and possibly lost, since GAE apps can usually ONLY run on GAE.