3 ms·

For Google cloud, I think before Cloud Run existed, they created a "create-with-container" option that deploys a container on a VM for you. https://cloud.googl

by kyrra 5y ago

For Google cloud, I think before Cloud Run existed, they created a "create-with-container" option that deploys a container on a VM for you. https://cloud.google.com/sdk/gcloud/reference/compute/instances/create-with-container https://cloud.google.com/sdk/gcloud/reference/compute/instan... (I'm a googler, but do not work anywhere near your cloud. I used this for a personal project.)

jillesvangurp 5y ago
That still exists. We actually switched to that from Cloud Run. Cloud Run was a little too restrictive with background threads in our application. These basically get throttled in between requests and we kind of needed them not to be throttled. Otherwise it is actually great and works as advertised. The process of switching to using simple vms was a gcloud one liner to spin up a vm with the same docker image. That basically worked the first time we tried it. We ran with this for a few months. Then we finally sat down and got ourselves a load balancer with an instance group and an instance template. We deploy by telling gcloud to replace the template on the instance group. It does a rolling restart and it uses our health checks to ensure it does the right things. And it's stupidly easy to script together. We use Github actions for automated deploys. It does rolling restarts, has health checks, monitoring, logging, etc. built in. Everything you need to run a simple monolith. It's similar to what Amazon did with ECS. Just less convoluted and way more easier to use. People assume they need all this crazy complicated infrastructure. But it's all commodity off the shelf stuff these days and it doesn't have to be that hard to set up. Could we automate the above? Sure. But what's the point. It's 1 command to create instance templates, another command to tell the LB to run it. Provisioning the LB with a wild card certificate is a five minute job using the UI. It will tell you the commands if you need them. But it's something you do once per environment.
- intrepidsoldier 5y ago
  Agreed. People choose technologies for their own reasons. The full spectrum is surviving and thriving: https://ramansharma.substack.com/p/multiple-stops-on-the-cloud-compute-continuum-all-with-their-own-merits-6b921ed82f2 https://ramansharma.substack.com/p/multiple-stops-on-the-clo...
pqb 5y ago
I am shocked, because I see it for the first time. Recently, I have been browsing gcloud documentation like a crazy to prepare myself to PCA certification but I have never seen this doc page before [0]. Thanks a lot for a mentioning it! [0]: https://cloud.google.com/compute/docs/containers/deploying-containers https://cloud.google.com/compute/docs/containers/deploying-c...

by kyrra 5y ago

jillesvangurp 5y ago

That still exists. We actually switched to that from Cloud Run. Cloud Run was a little too restrictive with background threads in our application. These basically get throttled in between requests and we kind of needed them not to be throttled. Otherwise it is actually great and works as advertised. The process of switching to using simple vms was a gcloud one liner to spin up a vm with the same docker image. That basically worked the first time we tried it. We ran with this for a few months. Then we finally sat down and got ourselves a load balancer with an instance group and an instance template. We deploy by telling gcloud to replace the template on the instance group. It does a rolling restart and it uses our health checks to ensure it does the right things. And it's stupidly easy to script together. We use Github actions for automated deploys. It does rolling restarts, has health checks, monitoring, logging, etc. built in. Everything you need to run a simple monolith. It's similar to what Amazon did with ECS. Just less convoluted and way more easier to use. People assume they need all this crazy complicated infrastructure. But it's all commodity off the shelf stuff these days and it doesn't have to be that hard to set up. Could we automate the above? Sure. But what's the point. It's 1 command to create instance templates, another command to tell the LB to run it. Provisioning the LB with a wild card certificate is a five minute job using the UI. It will tell you the commands if you need them. But it's something you do once per environment.

intrepidsoldier 5y ago
Agreed. People choose technologies for their own reasons. The full spectrum is surviving and thriving: https://ramansharma.substack.com/p/multiple-stops-on-the-cloud-compute-continuum-all-with-their-own-merits-6b921ed82f2 https://ramansharma.substack.com/p/multiple-stops-on-the-clo...

pqb 5y ago

I am shocked, because I see it for the first time. Recently, I have been browsing gcloud documentation like a crazy to prepare myself to PCA certification but I have never seen this doc page before [0]. Thanks a lot for a mentioning it! [0]: https://cloud.google.com/compute/docs/containers/deploying-containers https://cloud.google.com/compute/docs/containers/deploying-c...