Launchdock was / is really a prototype PaaS tool - and what we are currently using to launch demo shops / docker containers. It works reasonably well, and as a Meteor app, is also tuned for Meteor but in the long term, we’re also looking for another solution - as this wasn’t really meant to be my full time focus (and it’s clear it could be).
Tutum.io, Galaxy, Modulus, and Docker itself (with swarm,etc) are all working towards solutions that we’ll be testing. It’s not really the launching or scaling of Docker+Meteor containers that’s tough (relatively speaking), but as has been pointed out - the management and scaling of MongoDB is the real challenge. From what MDG has indicated to us, Galaxy is going to be Docker+Kubernetes tuned for Meteor, and the Meteor CLI. Tutum is a more agnostic way of creating Docker stacks “DB+HAProxy, app”, and is a nice (free) tool on top of your existing infrastructure.
We’re looking at launching and scaling 800-1500 full stack deployments (DB+Proxy+App) per month, and have tested various approaches with the 5000+ or so alpha shops we’ve launched at
I’ve tested our own physical DB cluster (4 R3 instances + MongoDirector), Compose.io Elastic Deployment, and both MongoDB+Meteor in a single container, and as linked db+app containers. With physical, or compose databases, the problems tend to be speed of instantiation, a 20,000 connection limit, and only being able to manage about 1800 databases on a single cluster. I’m thinking that best performing solution would likely be a persistent volume docker host + mongo containers… but haven’t tested this at scale yet. But db persistence and data migration, load balancing will all be challenges here as well.