4 ms·
We're still a ways away from having to make our choice of container orchestration framework(s), but it seems like it's getting to be an increasingly difficult d
by gtaylor 11y ago
We're still a ways away from having to make our choice of container orchestration framework(s), but it seems like it's getting to be an increasingly difficult decision to make. There are a lot of great pieces that can be used independently, alongside one another, or on top of another.
For example, Kubernetes + Mesos, Kubernetes + CoreOS, Mesosphere + CoreOS, Swarm + whatever else, etc.
I guess it's a good problem to have, but I'm looking at this as a question of what the jigsaw puzzle is going to look like for us in six months to a year. I'm not sure I buy the notion that all of this reduces complexity, it just shuffles it around.
- sanderjd 11y agoYep, I'm interested in this model, but finding it very hard to effectively evaluate all the permutations. This is hugely exacerbated by the fact that nothing really seems complete, so pros and cons could either be due to different design decisions, different priorities, or different levels of maturity, and it's very difficult to tell which.
- sfilipov 11y agoYou don't need to evaluate all permutations, at least not in detail as long as you know the main selling point of each. Go for the setup that has the smallest number of components yet is complete enough for your specific case. For me - it's a single CoreOS VM, no etcd or fleet, no higher level abstractions like Kubernetes or Mesosphere. Most people who need to get a bigger system running will need to take advantage of etcd and fleet + multiple VMs but can still decide that Kubernetes/Mesosphere is too much. And then there are the people who need the full package.
- sanderjd 11y agoI think most people looking into deploying a production system using containers will find themselves interested in evaluating the "full package", and also find themselves interested in more than just the main selling points. That's where my comment is coming from. YMMV I suppose!
- tracker1 11y agoFor me, it was three instances with dokku-alt, and deploying exactly the same to all three... fronted by two (load-balanced) caching/ssl-terminating nginx instances. Using my cloud provider's table storage for configuration (caching in an app module, that clears it's cached results every 5 minutes)... realistically my configuration doesn't change that much.
- otterley 11y ago> You don't need to evaluate all permutations, at least not in detail as long as you know the main selling point of each. I need to know how the software works in order to evaluate it effectively. Selling points don't tell me that; they are conjured up by marketers to influence managers, not engineers.
- jacques_chester 11y agoI'm talking my own book here, but: Cloud Foundry. It already works. You throw code at it, the code is staged, deployed, logged and monitored.