4 ms·

Just tried creating a service with the sample image and love the quick deployment time compared to AppEngine Flex. I noticed that the console shows a traffic p

by lxxvii 8y ago

Just tried creating a service with the sample image and love the quick deployment time compared to AppEngine Flex. I noticed that the console shows a traffic percentage for each revision, but no apparent way to change it. Any plans to support traffic splitting, or at least a one-click way to re-activate (or re-deploy) an older revision?

asciimike 8y ago
Yes, there are plans for traffic splitting. Currently Cloud Run only supports the `runLatest` mode of the Knative Serving spec (https://github.com/knative/serving/blob/master/docs/spec/spec.md#service https://github.com/knative/serving/blob/master/docs/spec/spe...) but we're working on other modes (e.g. `release`) which would allow for traffic splits.
crisscrosscrash 8y ago
When would you use Cloud Run vs App Engine Flex? Doesn't App Engine Flex essentially help you run an app in a container and handle scaling too? For example, what if you're running a stateless JVM app like something on Play Framework. Could you run it on either App Engine Flex or Cloud Run, and if so, what considerations would there be for choosing one over the other?
- asciimike 8y ago
  0. Flex doesn't scale to zero, Run does. 1. Flex runs directly on VMs (sharing some GCE networking, access to GPUs, etc.), Run doesn't. Those are the two that come up top of mind. We're working on a more comprehensive "choose your compute product" walkthrough in the near future.
  - crisscrosscrash 8y ago
    Comparison doc in the future would be great! It sounds like there's a bit of overlap. If I'm not up and running yet and just want the most managed solution (least work to run, with the most powerful high level features), is one of these a clear choice? In my case, I don't care as much about low level access, but I just want my app to run quickly and efficiently. App Engine Flex's ability to run multiple services within an application, get load balancing set up, have versions of the app for testing and rollbacks, etc seems great. However, overall I just want to the easiest way to run my stateless set of services.

by lxxvii 8y ago

asciimike 8y ago

Yes, there are plans for traffic splitting. Currently Cloud Run only supports the `runLatest` mode of the Knative Serving spec (https://github.com/knative/serving/blob/master/docs/spec/spec.md#service https://github.com/knative/serving/blob/master/docs/spec/spe...) but we're working on other modes (e.g. `release`) which would allow for traffic splits.

crisscrosscrash 8y ago

When would you use Cloud Run vs App Engine Flex? Doesn't App Engine Flex essentially help you run an app in a container and handle scaling too? For example, what if you're running a stateless JVM app like something on Play Framework. Could you run it on either App Engine Flex or Cloud Run, and if so, what considerations would there be for choosing one over the other?

asciimike 8y ago
0. Flex doesn't scale to zero, Run does. 1. Flex runs directly on VMs (sharing some GCE networking, access to GPUs, etc.), Run doesn't. Those are the two that come up top of mind. We're working on a more comprehensive "choose your compute product" walkthrough in the near future.
- crisscrosscrash 8y ago
  Comparison doc in the future would be great! It sounds like there's a bit of overlap. If I'm not up and running yet and just want the most managed solution (least work to run, with the most powerful high level features), is one of these a clear choice? In my case, I don't care as much about low level access, but I just want my app to run quickly and efficiently. App Engine Flex's ability to run multiple services within an application, get load balancing set up, have versions of the app for testing and rollbacks, etc seems great. However, overall I just want to the easiest way to run my stateless set of services.