4 ms·
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
by 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 agoYou 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 agoI'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.