orchestration

But orchestration is about coordination, often of dissimilar things; that means dealing with different APIs, end-points, and subsystems.

This is because Docker is building it's own scheduling/orchestration tools, which is what Kubernetes is for.

As it is, Mesos is more of an SDK than anything, giving you the tools to write an orchestration system.

Ah, so you need to use proprietary SaaS in order to have decent orchestration?

A full orchestration and resource scheduling stack that scales with load even more so.

For example, orchestration has been simplified with hosted services like Tutum and Cloud66.

My company is exploring our options in the container orchestration space and have been testing out kubernetes on aws in the past week.

It's a management and orchestration layer on the top of Docker.

I would say go has far easier primitives to be a tool for orchestration.

Mesos is definitely more mature, and you can use Marathon for container orchestration, which is a little more mature than Kubernetes, but it's also a bit simpler.

I have rarely met developers that are excited to do operations work like defining and implementing system security policies, change control, and orchestration.

How does this compare to Docker's fig-based orchestration solution??

Still using docker to streamline deployments though, but one docker container/role per instance, no "orchestration" for containers (baked AMIs, ASGs).

"Oops" only works when there's no proof, and it's hard to hvae an absence of proof in something that would take so much orchestration.

"Public Cloud" and "Private Cloud" are pretty standard industry terms for using the same orchestration systems on your own data center vs.

Orchestration may take more time to nail down and standardize.