Save yourself from a disaster: Redundancy on a budget

What can we learn from the latest major cloud incident (ie. burning OVH datacenter)? Do not put all your eggs in one basket!
The only certain thing is that it’s not a matter of IF there’ll be a disaster but rather WHEN, so better be not caught off guard.

When your data center is on fire… how will RavenDB react? | RavenDB NoSQL
Fire at Our Strasbourg Site

I’m running a bunch of very small websites (with very simple infrastructure topology) and I wanted to put in practice something on a budget. So, I’ve decided to go multi-cloud.

Evolution

I’ve started with an infrastructure that looked like this:

Then, I ended up with something like this:

Outline

This is the outline plan I followed to upgrade my infrastructure:

  1. Secure the Database
  2. Secure the Storage
  3. Redundancy of Database
  4. Redundancy of Storage
  5. Redundancy of Web Servers
  6. Redundancy of DNS
  7. Billing Impact
  8. Manual Configurations
  9. Disaster Recovery Plan
  10. Play with Providers

I’ll publish each week the details of each step I took to make my website disaster-proof while keeping my cloud spending on a tight leash (so you could do this too).


Stay tuned.

Check out the whole version of this post in the ebook.