4 ms·

Well, that was fast... After the announcement of Amazon Container Registry docker had to make some move and this is a great one. Congrats to the tutum team, th

by joeyspn 11y ago

Well, that was fast... After the announcement of Amazon Container Registry docker had to make some move and this is a great one. Congrats to the tutum team, they have built a really nice project that makes really easy to build and maintain container pipelines. Can't wait to see the integrations with the other docker tools...

nickstinemates 11y ago
> After the announcement of Amazon Container Registry docker had to make some move and this is a great one. This has been in the works for much longer than that. The Tutum team built a pretty amazing product that their users love, and the passion, excitement, and forethought both Borja and Fernando have around the space has impressed me since I met them in October of 2013.
- joeyspn 11y ago
  > This has been in the works for much longer than that. I meant (as a user) that Docker Hub was at risk of losing its appeal because probably couldn't rival AWS's registry (pricing, speed, etc). IMO this move gives Docker a breath of fresh air ... What's gone fast is the trajectory of these guys from launch (they're not even out of beta) to acquisition.. So, congrats to both teams!
  - nickstinemates 11y ago
    Interesting perspective, thanks.
cwilkes 11y ago
Speaking of Amazon, I thought that docker was going to hit their bottom line as now people could easily fully utilize their ec2 instances and thus cutting into their already thin margins. However they jumped past this problem with Lambda. Because in the end I don't want to run an operating system. I don't even want to run tomcat. I just want to run a function in tha cloud. Docker makes it easier to shovel around your application while lambda is the next phase of cloud development.
- joeyspn 11y ago
  > Docker makes it easier to shovel around your application while lambda is the next phase of cloud development. Yes, lambda and friends (AWS Mobile Hub, JAWS Stack, etc) are the next paradigm, but it's not ripe yet. For instance the newly introduced cronjob only allows 5 mins periods as minimum, when for one of my projects I needed full cron precision (I was starting to build on Lambda and had to return to docker...) Maybe in 6-12 months thing will be fully ready...
  - stephenitis 11y ago
    You should test out IronWorker which allows for 1-2 hours per task run, more languages, and supports docker images for your runtime environments. Although it not as price conscious as lambda it is definitely more feature rich and easy to use. (I used to work for Iron.io)
- willcodeforfoo 11y ago
  I'm waiting for AWS Lambda to support running a Docker container, right now its just Node.js or Java with a specified environment. I suspect they are running Lambda functions in containers already, hopefully just a matter of time before they expose that to any Docker image.

by joeyspn 11y ago

nickstinemates 11y ago

> After the announcement of Amazon Container Registry docker had to make some move and this is a great one. This has been in the works for much longer than that. The Tutum team built a pretty amazing product that their users love, and the passion, excitement, and forethought both Borja and Fernando have around the space has impressed me since I met them in October of 2013.

joeyspn 11y ago
> This has been in the works for much longer than that. I meant (as a user) that Docker Hub was at risk of losing its appeal because probably couldn't rival AWS's registry (pricing, speed, etc). IMO this move gives Docker a breath of fresh air ... What's gone fast is the trajectory of these guys from launch (they're not even out of beta) to acquisition.. So, congrats to both teams!
- nickstinemates 11y ago
  Interesting perspective, thanks.

cwilkes 11y ago

Speaking of Amazon, I thought that docker was going to hit their bottom line as now people could easily fully utilize their ec2 instances and thus cutting into their already thin margins. However they jumped past this problem with Lambda. Because in the end I don't want to run an operating system. I don't even want to run tomcat. I just want to run a function in tha cloud. Docker makes it easier to shovel around your application while lambda is the next phase of cloud development.

joeyspn 11y ago
> Docker makes it easier to shovel around your application while lambda is the next phase of cloud development. Yes, lambda and friends (AWS Mobile Hub, JAWS Stack, etc) are the next paradigm, but it's not ripe yet. For instance the newly introduced cronjob only allows 5 mins periods as minimum, when for one of my projects I needed full cron precision (I was starting to build on Lambda and had to return to docker...) Maybe in 6-12 months thing will be fully ready...
- stephenitis 11y ago
  You should test out IronWorker which allows for 1-2 hours per task run, more languages, and supports docker images for your runtime environments. Although it not as price conscious as lambda it is definitely more feature rich and easy to use. (I used to work for Iron.io)
willcodeforfoo 11y ago
I'm waiting for AWS Lambda to support running a Docker container, right now its just Node.js or Java with a specified environment. I suspect they are running Lambda functions in containers already, hopefully just a matter of time before they expose that to any Docker image.