February 18, 2016
Ep. #3 Feat. Redpoint’s Scott Raney and Lenny Pruss
Tom, Scott, and Lenny discuss Redpoint's investment philosophy, the changing expectations founders and investors have for each other, and fi...
There’s a reason Docker just raised a $95M funding round. The promise of containers running asynchronously in the cloud means the opportunity for greater developer productivity and agility. But the problem here isn’t containerizing services, it’s ensuring that all of these distributed and asynchronous workloads are working together as a single organism. Iron.io believes that DockerWorker is the key to a better workflow.
In a recent Heavybit Show and Tell, CEO of Iron.io Chad Arimura, introduced DockerWorker — a product that replicates in-production Docker containers for the test, build and deployment process.
Since all Iron.io tasks run in Docker containers, developers can use DockerWorker to build and test locally and then deploy an exact replica of their code package in the cloud when it’s ready for production.
This improved process removes latencies associated with library loading, service dependencies, and upload times. Once the code resides on the Iron.io platform, developers enjoy all the benefits of being able to queue tasks and achieve scalable workflows with almost zero dev ops. The result is reduced development (build and test) times, shorter deployment cycles (push to platform), and better scale and availability (production).
With this new Iron.io workflow, code iterations move from minutes to seconds. For more on how Iron.io’s DockerWorker model works (via CLI or API), check out Arimura’s presentation:
For more info on the DockerWorker workflow, check out Iron.io’s post on DockerWorker. They’ve also included a repository with examples in a bunch of different languages so you can try it out for yourself.