Docker 1.12: Now with Built-In Orchestration

Re:Docker 1.12: Now with Built-In Orchestration by zamalek on Monday June 20, 2016 @04:08PM (#11941074)

> your database gets rescheduled and emptied along the way

That's bundling an CP application into seemingly AP infrastructure (from what I gleaned from their docs). Completely the wrong tool for the job. If the application was designed for that it would have recovered. In your defense, they have nothing to warn about that in their documentation.

[ Parent | on HN ]

Re:Docker 1.12: Now with Built-In Orchestration by jdoliner on Monday June 20, 2016 @06:00PM (#11941927)

This isn't really a CAP theorem problem and it's certainly not right to describe Docker as "AP infrastructure." What would that mean exactly? Would you expect this problem to go away if I used a database that sacrificed consistency for availability such as Riak?

[ Parent | on HN ]

Re:Docker 1.12: Now with Built-In Orchestration by zamalek on Tuesday June 21, 2016 @03:30AM (#11944053)

Swarm (not the whole of Docker) seems like something designed for databases like Riak, yes. A SQL failover cluster might work, but certainly not a single database container on infrastructure designed for highly available apps.

[ Parent | on HN ]