Docker 1.6: Engine and Orchestration Updates, Registry 2.0, and Windows Client
I'm finding that the distinction between Swarm, Compose, and Machine is not <i>immediately</i> obvious.  Docker would probably benefit to "you should use this when", kind of logic, between the two.<p>Clearly, Swarm is the lightweight "cloud" thing (yay!), but if I'm deploying to Swarm, do I use Machine or Compose?  Etc.<p>Possibly too many nouns would be made simpler by a single command line tool with subcommands, that were less skeomorphic, and instead were named after what they did.<p>Just my two cents, but the documentation needs to explain a bit more of the basics at a high level before going into the weeds, IMHO.<p>The other gotcha page is "if I'm on Amazon", when would I want to use swarm, if at all, when I had ECS, and how much remains relevant?  I'm guessing not so much still applies, but perhaps I'm wrong.<p>Another good article would be what parts of these new tools remain relevant if I'm using, say, CoreOS (fleet), Kubernetes, or Mesos, or OpenStack with Docker.  I'm not saying the others are better, it's just difficult to visualize how they interplay.