In my view what we&#x27;re really talking about here is PaaS.  Every shop is left to implement a private PaaS on their own for the most part.  There are software companies out there who specialize in helping teams deploy this kind of architecture for example:<p><a href="https:&#x2F;&#x2F;pivotal.io&#x2F;platform" rel="nofollow">https:&#x2F;&#x2F;pivotal.io&#x2F;platform</a><p><a href="http:&#x2F;&#x2F;deis.io&#x2F;" rel="nofollow">http:&#x2F;&#x2F;deis.io&#x2F;</a><p>both are open source technologies based on Docker that are gathering momentum and you can hire consultants to help you deploy either one.<p>I personally don&#x27;t use Docker.  The startup I&#x27;m building has chosen to standardize on the JVM for all application code so we leverage the JAR file as a kind of container.  The Java ecosystem already solved the problem of zero-downtime deployments a long time ago so for us deploying can be as simple as shipping new jars file across the network.<p>Instead of using Docker to drive development we simply spin up development database&#x2F;redis&#x2F;etc instances in the cloud which automatically join a development VPN network.  All of the non-VPN interfaces are automatically firewalled off.  One nice advantage of this setup is that developers who have slow laptops are still able to work.  I&#x27;m a big fan of this approach.<p>Check out Wildfly&#x27;s &quot;High Availablity&quot; features if you&#x27;re interested in one way that the Java Ecosystem can make headaches like zero-downtime deployment, HTTP health checks, monitoring, caching, and even load balancing disappear.. It&#x27;ll deploy non-java code too as long as it&#x27;s on the JVM.  If you&#x27;re a Scala only shop there are some great Scala-only alternatives available to boot.