4 ms·

This might be a better link: https://cloud.google.com/run/docs/ https://cloud.google.com/run/docs/ "Cloud Run is a managed compute platform that enables you to

This might be a better link: https://cloud.google.com/run/docs/ https://cloud.google.com/run/docs/ "Cloud Run is a managed compute platform that enables you to run stateless containers that are invocable via HTTP requests. Cloud Run is serverless: it abstracts away all infrastructure management, so you can focus on what matters most — building great applications. It is built from Knative, letting you choose to run your containers either fully managed with Cloud Run, or in your Google Kubernetes Engine cluster with Cloud Run on GKE.". So, like lambda but with containers. Pretty much what I have wanted since I first started learning about Docker.

WestCoastJustin 8y ago
FYI - I just posted a review video where I walk through Cloud Run doing some demos. Check it out at: https://sysadmincasts.com/episodes/69-cloud-run-with-knative https://sysadmincasts.com/episodes/69-cloud-run-with-knative
deleted 8y ago
[deleted]
aelzeiny 8y ago
As someone who works in Data Engineering, I'm a big fan of cloud-based docker containers with services like AWS Fargate/Google Run. It allows us to be able to pay for resource use rather than provisioning. For the longest time I had to justify the additional cost and constant maintenance of an n-th server just to accommodate for capacity at peak hours. Anecdotally, most of our batch jobs don't need high availability, so the startup time of a server-less docker is an acceptable trade-off to parallelism.
- wtmt 8y ago
  > It allows us to be able to pay for resource use rather than provisioning. Not arguing against the choice, but at some level, you are paying for the provisioning costs of the cloud provider. The higher initial costs of provisioning is what you may be escaping, and instead paying on an ongoing basis (as if you’re leasing equipment and services). Once your needs scale significantly, cloud providers would end up being quite expensive if your load is not highly variable.
  - chrisbroadfoot 8y ago
    It's compatible with Knative, which is easy to set up in GKE, so you can migrate loads over to that if you want more control over your compute costs. And of course, you can run Knative outside of GKE, too. Disclaimer: I work on GCP but have only touched Cloud Run/Knative a little bit.
  - cwyers 8y ago
    > if your load is not highly variable Most real-world loads are in fact pretty variable.
- kortilla 8y ago
  You know you can also boot instances that bill at hour and less granularity right? Billing is probably the least compelling argument to a service like this.
nilkn 8y ago
This seems like a competitor more to Fargate than to Lambda, right?
- throw03172019 8y ago
  Definitely seems like it.
- ilogik 8y ago
  With Fargate you have containers running all the time, and you pay for that....from what I've seen of Cloud Run, you just pay when you're actually serving requests
  - asciimike 8y ago
    With Cloud Run you're only paying for resources used, and with Cloud Run on GKE you're paying for the underlying cluster [1]. This also gives you the flexibility to optimize costs by shifting workloads between the two if desired. [1] https://cloud.google.com/run/pricing https://cloud.google.com/run/pricing
- alpb 8y ago
  Closer to Lambda from a lifecycle perspective, because your code runs only when there’s a request (and you’re billed only during requests). But also Closer to Fargate from a programming paradigm perspective, as the deployment unit is “container image”.
SlowRobotAhead 8y ago
First off, thanks for the overview text. I really hate how many tech people just assume ‘you’ know what they mean because ‘they’ know what they mean. It’s like they’re trying to accentuate the autistic stereotypes! >Pretty much what I have wanted since I first started learning about Docker. Why? I have a use for lambdas in an application I’m working on. But I don’t really get why you want stateless containers that spool up and down on demand. Is it for things like “I need this entire existing program to run and can’t refactor it to a lambda itself”? I only need to do some API processing and data we work, so I’m not entirely sure what starless containers are for. Might be a dumb question!
- ec109685 8y ago
  Go Cloud Run: https://cloud.google.com/run/docs/quickstarts/build-and-deploy https://cloud.google.com/run/docs/quickstarts/build-and-depl... Vs. Go Lambda: https://docs.aws.amazon.com/lambda/latest/dg/go-programming-model-handler-types.html https://docs.aws.amazon.com/lambda/latest/dg/go-programming-... The Cloud Run steps aren't that complex and you get something you can easily run on your local computer too.
  - aynsof 8y ago
    You can definitely run Lambda functions locally, too: https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-invoke.html https://docs.aws.amazon.com/serverless-application-model/lat...
    - ec109685 8y ago
      Good point. Though you still have “the cloud” calling your function versus truly having everything local.
aitchnyu 8y ago
Can it do serverful things like run cron jobs, suffer no warmup time, maintain efficient connections to Postgresql?
- merb 8y ago
  from the description you will suffer warmup time, you just need to start a http server withing 4 minutes. also cron jobs do not work since the computations only work as long as the container is running. it also still does not support .net since gvisior does not support it :( https://cloud.google.com/run/docs/reference/container-contract https://cloud.google.com/run/docs/reference/container-contra... https://cloud.google.com/run/docs/issues https://cloud.google.com/run/docs/issues it's basically AppEngine v3 (without long running stuff)
- jganetsk 8y ago
  cron jobs in knative: https://www.knative.dev/docs/eventing/samples/cronjob-source/ https://www.knative.dev/docs/eventing/samples/cronjob-source...
merb 8y ago
it's like appengine, but better!
alexellisuk 8y ago
So what OpenFaaS/OpenFaaS Cloud has been doing for 3 years :-)
- alpb 8y ago
  With a subtle difference like you don’t have to manage the infrastructure that runs the machinery. :)

WestCoastJustin 8y ago

FYI - I just posted a review video where I walk through Cloud Run doing some demos. Check it out at: https://sysadmincasts.com/episodes/69-cloud-run-with-knative https://sysadmincasts.com/episodes/69-cloud-run-with-knative

deleted 8y ago

[deleted]

aelzeiny 8y ago

As someone who works in Data Engineering, I'm a big fan of cloud-based docker containers with services like AWS Fargate/Google Run. It allows us to be able to pay for resource use rather than provisioning. For the longest time I had to justify the additional cost and constant maintenance of an n-th server just to accommodate for capacity at peak hours. Anecdotally, most of our batch jobs don't need high availability, so the startup time of a server-less docker is an acceptable trade-off to parallelism.

wtmt 8y ago
> It allows us to be able to pay for resource use rather than provisioning. Not arguing against the choice, but at some level, you are paying for the provisioning costs of the cloud provider. The higher initial costs of provisioning is what you may be escaping, and instead paying on an ongoing basis (as if you’re leasing equipment and services). Once your needs scale significantly, cloud providers would end up being quite expensive if your load is not highly variable.
- chrisbroadfoot 8y ago
  It's compatible with Knative, which is easy to set up in GKE, so you can migrate loads over to that if you want more control over your compute costs. And of course, you can run Knative outside of GKE, too. Disclaimer: I work on GCP but have only touched Cloud Run/Knative a little bit.
- cwyers 8y ago
  > if your load is not highly variable Most real-world loads are in fact pretty variable.
kortilla 8y ago
You know you can also boot instances that bill at hour and less granularity right? Billing is probably the least compelling argument to a service like this.

nilkn 8y ago

This seems like a competitor more to Fargate than to Lambda, right?

throw03172019 8y ago
Definitely seems like it.
ilogik 8y ago
With Fargate you have containers running all the time, and you pay for that....from what I've seen of Cloud Run, you just pay when you're actually serving requests
- asciimike 8y ago
  With Cloud Run you're only paying for resources used, and with Cloud Run on GKE you're paying for the underlying cluster [1]. This also gives you the flexibility to optimize costs by shifting workloads between the two if desired. [1] https://cloud.google.com/run/pricing https://cloud.google.com/run/pricing
alpb 8y ago
Closer to Lambda from a lifecycle perspective, because your code runs only when there’s a request (and you’re billed only during requests). But also Closer to Fargate from a programming paradigm perspective, as the deployment unit is “container image”.

SlowRobotAhead 8y ago

First off, thanks for the overview text. I really hate how many tech people just assume ‘you’ know what they mean because ‘they’ know what they mean. It’s like they’re trying to accentuate the autistic stereotypes! >Pretty much what I have wanted since I first started learning about Docker. Why? I have a use for lambdas in an application I’m working on. But I don’t really get why you want stateless containers that spool up and down on demand. Is it for things like “I need this entire existing program to run and can’t refactor it to a lambda itself”? I only need to do some API processing and data we work, so I’m not entirely sure what starless containers are for. Might be a dumb question!

ec109685 8y ago
Go Cloud Run: https://cloud.google.com/run/docs/quickstarts/build-and-deploy https://cloud.google.com/run/docs/quickstarts/build-and-depl... Vs. Go Lambda: https://docs.aws.amazon.com/lambda/latest/dg/go-programming-model-handler-types.html https://docs.aws.amazon.com/lambda/latest/dg/go-programming-... The Cloud Run steps aren't that complex and you get something you can easily run on your local computer too.
- aynsof 8y ago
  You can definitely run Lambda functions locally, too: https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-invoke.html https://docs.aws.amazon.com/serverless-application-model/lat...
  - ec109685 8y ago
    Good point. Though you still have “the cloud” calling your function versus truly having everything local.

aitchnyu 8y ago

Can it do serverful things like run cron jobs, suffer no warmup time, maintain efficient connections to Postgresql?

merb 8y ago
from the description you will suffer warmup time, you just need to start a http server withing 4 minutes. also cron jobs do not work since the computations only work as long as the container is running. it also still does not support .net since gvisior does not support it :( https://cloud.google.com/run/docs/reference/container-contract https://cloud.google.com/run/docs/reference/container-contra... https://cloud.google.com/run/docs/issues https://cloud.google.com/run/docs/issues it's basically AppEngine v3 (without long running stuff)
jganetsk 8y ago
cron jobs in knative: https://www.knative.dev/docs/eventing/samples/cronjob-source/ https://www.knative.dev/docs/eventing/samples/cronjob-source...

merb 8y ago

it's like appengine, but better!

alexellisuk 8y ago

So what OpenFaaS/OpenFaaS Cloud has been doing for 3 years :-)

alpb 8y ago
With a subtle difference like you don’t have to manage the infrastructure that runs the machinery. :)