Recommended high availability strategy?

  • Posted April 15, 2013

So, hardware fails every once in a while. What is the DO best practice for handling this?

At the moment I can only see:

  1. Set up a distributed filesystem across multiple DO nodes, ie Gluster (means high latency for writes)
  2. Use DNS round robin and/or failover. Problems with browser and proxy caching.

But perhaps in the near future you will support:

  • Floating ip
  • Floating VM images

Any other options? Thanks


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hey friend!

You might be happy to hear that we do have floating IPs now. You can find some information about it here:

Certainly the conversation for achieving true failover and redundancy is a larger one, of which this is merely a piece. However, having that piece is something that I think is extremely important. It lays a lot of the ground work for creative solutions on the customer side.


In the future we will be supporting something similar to a floating IP but not a floating VM and we don’t have a clear ETA on that. <br> <br>Otherwise HA really requires a more in depth conversation about what services you are running and what kind of availability and fault tolerance you want to build in.