Longer blog post here: <a href="http:&#x2F;&#x2F;dna.hioscar.com&#x2F;2015&#x2F;10&#x2F;14&#x2F;scaling-deployments-at-oscar&#x2F;" rel="nofollow">http:&#x2F;&#x2F;dna.hioscar.com&#x2F;2015&#x2F;10&#x2F;14&#x2F;scaling-deployments-at-osc...</a><p>We work out of a mono-repo and use pants (<a href="https:&#x2F;&#x2F;pantsbuild.github.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;pantsbuild.github.io&#x2F;</a>) for python&#x2F;jvm&#x2F;js packaging to deploy on mesos (<a href="https:&#x2F;&#x2F;mesos.apache.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;mesos.apache.org&#x2F;</a>). Pants gives us (effectively) the same development workflow as in production and let&#x27;s us treat any application (we have ~500 at this point) as just a command line executable (for things with weird lib dependencies, we do statically compiled wheels for each architecture - CentOS and OS X in our case - on our own pypi mirror). We&#x27;ve got a few kinks to still workout for local development of web projects (mostly related to JS&#x2F;CSS) but for things that don&#x27;t touch the frontend it&#x27;s pretty beautiful.