News for hackers. Stuff that matters.
Re:Docker not ready for primetime by 20yrs_no_equity on Sunday August 28, 2016 @05:25PM (#12378626)
Network partitions really do happen! They are often short, but if you can't recover from them, then you shouldn't call yourself a distributed system.

I am shocked at how fragile etcd is in this way. I was hoping docker swarm was better, but I'm not surprised (alas) to find out that it has the same problem.

I'm about ready to build my own solution, because I know a way to do it that will be really robust in the face of partitions (and it doesn't use RAFT, you probably should not be using RAFT, I've seen lots of complaints about zookeeper too. I've done this before in other contexts so I know how to make it work, but so have others so why are people who don't know how to make it work reinventing the wheel all the time?)

Re:Docker not ready for primetime by helloiamaperson on Sunday August 28, 2016 @07:27PM (#12379053)
I'd love to hear more about your solution. Are you saying that you've created an algorithm distinct from paxos/raft/zab that's more robust?
Re:Docker not ready for primetime by ldehaan on Monday August 29, 2016 @02:19PM (#12383928)
Check out weave, it's great for service discovery. Zookeeper is much better than etcd imo.
Re:Docker not ready for primetime by forktheweb on Sunday August 28, 2016 @07:25PM (#12379045)
amazon efs + duplicity p.o.t. snapshots -> s3 + docker = win