5 ms·
Heavy Docker user. Played with but have not used them, because Docker+machine+fig (now compose) already gives me everything I need (isolation, repeatable build,
by renegar 12y ago
Heavy Docker user. Played with but have not used them, because Docker+machine+fig (now compose) already gives me everything I need (isolation, repeatable build, atomic deploy) without another infra layer to worry about.
Then again, I'm a one-man 360 shop and a control freak, and I'm not afraid to slap together a webhook-eating build+deploy process on a whim. So, my use case is probably not representative of Docker users in general.
- smt88 12y agoDo you deploy in clusters? That's my main gap with Docker, and I haven't decided how to cover it. Deis[1] is the frontrunner at the moment, but a DIY solution is more appealing to me. I like to understand all the parts of my stack that I can. 1. http://deis.io http://deis.io
- eropple 12y agoI do deploy in clusters, and Mesos is pretty much the default for me. It's much, much smarter in terms of work allocation than Deis or the like, it's not tied strictly to Docker, and, having been in its codebase, I trust its engineering much more than the alternatives. It's cautiously-designed software, and it is the better for it. I would emphatically advise against rolling your own unless it's for projects you don't otherwise care about. Security and scalability are not trifles, and everybody else has already stepped on the rakes.