About traditional database high availability, the method is like:

  • master-master replication
  • master-slave replication
  • automatic failover

If use container to do that, we can use these ways:

  • Use busybox to save data, but how to do when the data goes large if only use container?
  • Use volume feature to sync data from container to hard disk. This way can do replication as traditional way
  • Connect database from application container. Then the next thing is the same as traditional way
  • Use large storage service like OpenStack Swift or AWS EBS. Maybe this way can save the data well depend on third party services.

At least, the first choice, use pure container technology, is there a way to do high availability?

  • you've listed many different container and hosting options. Would you edit your post to limit the question to be more specific, otherwise it is way too broad. Jul 27 '17 at 2:57
  • @SeanGallardy As I wrote, I want to confirm the first choice, use only container like busybox to save data. Then how to do. Jul 27 '17 at 3:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.