Hacker News new | comments | show | ask | jobs | submit login

So, in thinking about how to mitigate unforeseen disasters while trying to maintain anonymity - I think the following solution to such a problem would be really easy (not free, but easy)

Host your site/content across multiple cloud providers. Then host VPS web servers with other providers and have them balance between the backend cloud servers.

Then put cloudflare on top of that.

Ideally, you would want to have multiple service instances with the cloud providers which are silo'd from each other - but exact duplicates (e.g. they are under fully different accounts with the cloud provider)

Your front-end web servers keep a cache of content from the cloud servers - and they are pushed to. For even lower-end content needs, you can pull from a drop box account or something.

Any of the front end gear gets seized - You can bring it up with a VPS image really quickly.

Then host VPS web servers with other providers and have them balance between the backend cloud servers.

If you don't know what the word latency means, this setup will teach you all about it.

Another problem is that your various providers will probably charge you for WAN bandwidth. So you will pay three times for every request: Twice from backend to balancer (one charge from provider A, one from provider B) plus another charge to send the same data back out from the balancer to the customer.

Plus you will be miserable trying to keep your site up 100% of the time across two cloud providers. Have a problem on either one, and 50% of your capacity will go offline.

Might be better to realize that "my servers were seized by the FBI" is a rare occurrence and you can probably afford a few hours' worth of downtime and/or data loss. Make offsite backups from your primary provider on a relatively long timescale (once per day, maybe once per hour if you're more sensitive; live database replication for the crazy-sensitive) and have a procedure for spinning those up at a secondary provider. Test that procedure every month or so. The beautiful thing about cloud services is that you can pay for your emergency-backup servers by the hour and only when you are using them, or testing them.

Yes, I was not trying to mitigate latency. I was trying to maximize resiliency.

If you're doing something where you might get the FBI seizing your servers - maybe latency is not a paramount concern.

Capacity might also not be of primary importance.

I am just trying to find the 100% most resilient form of online hosting that masks the layers as much as possible.

The tin-foil-hat in me can see many many reasons why one would want to be aware of how to accomplish something like this.

Even easier, you use Softlayer and use their global load balancer.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact