3 ms·

I use Google Cloud Run to run my serverless code for exactly this reason. GCR is literally just a container that runs on demand (with scaling to 0). Literally

I use Google Cloud Run to run my serverless code for exactly this reason. GCR is literally just a container that runs on demand (with scaling to 0). Literally the only GCR specific part is making sure the service listens on the PORT env. If I was so inclined, I could deploy the exact same container on any number of services, host it myself and/or run it on my laptop for development purposes. There's also Kubernetes Knative which is basically (afaik) self hosted GCR.

jononor 6y ago
How is the spin-up time for such a container?
- nikon 6y ago
  In my experience pretty good, even for a Django app. I believe the container sticks around for a while and is throttled to 0 CPU.
- Simon321 6y ago
  a few seconds apparently: https://thenewstack.io/comparison-aws-fargate-vs-google-cloud-run-vs-azure-container-instances/ https://thenewstack.io/comparison-aws-fargate-vs-google-clou...
- ko5ta 6y ago
  It varies massively based on the tech stack. I have seen both simple Spring Boot and Quarkus apps take in excess of 10 seconds to start up in JVM mode. However, Quarkus compiled to native binary with GraalVM starts consistently under a second (in the ~500ms range). This is still brutal compared to running it on a vanilla MacBook which usually takes less than 20ms.
Can_Not 6y ago
Cloud Run is excellent if I wrote my own application. My biggest issue is that most off the shelf open source software that has a docker container often use a complicated docker compose file so if they can be deployed, they might be waiting on each other's cold starts (which can be very long and expensive) and/or need more databasesish things than I want. So obvious mistakes and unrealistic expectations aside, I have several nodejs and crystal apps on cloud run which is running well and just the concept "lambda for docker containers" is pretty awesome. Cold starts are pretty harsh ATM, hopefully they improve.

jononor 6y ago

How is the spin-up time for such a container?

nikon 6y ago
In my experience pretty good, even for a Django app. I believe the container sticks around for a while and is throttled to 0 CPU.
Simon321 6y ago
a few seconds apparently: https://thenewstack.io/comparison-aws-fargate-vs-google-cloud-run-vs-azure-container-instances/ https://thenewstack.io/comparison-aws-fargate-vs-google-clou...
ko5ta 6y ago
It varies massively based on the tech stack. I have seen both simple Spring Boot and Quarkus apps take in excess of 10 seconds to start up in JVM mode. However, Quarkus compiled to native binary with GraalVM starts consistently under a second (in the ~500ms range). This is still brutal compared to running it on a vanilla MacBook which usually takes less than 20ms.

Can_Not 6y ago

Cloud Run is excellent if I wrote my own application. My biggest issue is that most off the shelf open source software that has a docker container often use a complicated docker compose file so if they can be deployed, they might be waiting on each other's cold starts (which can be very long and expensive) and/or need more databasesish things than I want. So obvious mistakes and unrealistic expectations aside, I have several nodejs and crystal apps on cloud run which is running well and just the concept "lambda for docker containers" is pretty awesome. Cold starts are pretty harsh ATM, hopefully they improve.