4 ms·
Posts like this are interesting, I felt it started out about "I'm going to teach you about docker" and then shifted into a piece about general technical decisio
by dayjah 11y ago
Posts like this are interesting, I felt it started out about "I'm going to teach you about docker" and then shifted into a piece about general technical decision making; and being pragmatic.
Docker has fast become my world: from local development and detailing of dev setups through to deployment of apps using ElasticBeanstalk's single-container Docker pattern.
The dev setup piece is seeming the most valuable currently. That you can land in a project that I've been in and issue `docker-compose build`, `docker-compose up` and have a fully functioning development server without the need of installing a half dozen dependencies locally really does feel like a positive.
As a devopsy-leaning person the "single binary" deployment it lends toward is beautiful too. Pragmatism always though: for many of our services the network IO impact is undesirable, so we use go (statically linked binaries) on bare metal for those.
- tylfin 11y agoIs this network IO impact still an issue? http://stackoverflow.com/questions/21889053/what-is-the-runtime-performance-cost-of-a-docker-container http://stackoverflow.com/questions/21889053/what-is-the-runt...