|
|
|
|
|
|
by brudgers
3579 days ago
|
|
|
Context for my random thoughts from the internet: I don't use Swarm in production but I read the blog post. 1. Everyone has their definition of 'prime time'. Kubernetes is a 'third system' designed by Google to meet Google's 'prime time' needs. 2. The odds are that if your company's 'prime time' needs were similar to Google's, writing your own container orchestration layer would be a viable option and there's a good chance it would already have been done. 3. My take on the blog post was that the author was probably imagining a context containing more than a few bare metal nodes. 4. If Docker Swarm works for your organization, there's no reason not to use it. A few bare metal nodes seems to be one of the use cases for which it was built. The difference I see is that Kubernetes is a solution and Docker Swarm is a product. By which I mean that Kubernetes was designed around Google's internal technical needs and Docker Swarm was designed around the needs of Docker's customer base. That doesn't make either right or wrong in general, but it may mean that one or the other is a better fit for a particular organization. Good luck. |
|
|