3 ms·

What’s the advantage of GCR over AWS Fargate/ECS? I’ve been running an app on ECS for a couple months now and have been pretty happy with the ease of set-up, lo

What’s the advantage of GCR over AWS Fargate/ECS? I’ve been running an app on ECS for a couple months now and have been pretty happy with the ease of set-up, load-balancing, auto-scaling etc, though there are still kinks I’m figuring out (SSHing into containers to perform database management, for example, or deploying updated tasks without downtime). Is the main selling point of GCR just its price? I haven’t found ECS pricing to be an issue (but I’m also not running anything at scale, and I do pay more than a few cents a month — but still under 10 bucks).

mmbleh 7y ago
GCR runs containers like Fargate, but scales to zero like lambda, so you only pay for usage
- skj 7y ago
  GCR is the container registry and does nothing but store your artifacts.
  - PhilippGille 7y ago
    The article and comments are about Google Cloud Run
anirudhgarg 7y ago
I don't think you can scale up and scale down Fargate based on Http requests
- staticassertion 7y ago
  I'm not sure if you can reasonably scale to 0, but I believe you can attach Autoscaling Groups to Fargate.
  - anirudhgarg 7y ago
    Most likely it would be based on CPU/Memory and not requests
    - reilly3000 7y ago
      Most definitely, but you can auto scale on custom metrics with a bit of glue. Even a very small node app has a start time in the 10-30 sec range. Every auto scaling system, even cloud run, can struggle to keep up with extremely bursty traffic. If you want no timeouts, you have to overprovision.
asdfasdfgdy 7y ago
Disclaimer: I work on cloud run Another advantage not stated by others is that cloud run (mostly) adheres to the KNative API spec. This allows you lift-and-shift your application from cloud run to a Kubernetes cluster with the KNative plugin installed, a feature you can’t find with any other serverless product
- ignoramous 7y ago
  Thanks. What are the usual cold start and warm start times for Cloud Run? Is there potential for those start times to go down to a few milliseconds in the near-future?

mmbleh 7y ago

GCR runs containers like Fargate, but scales to zero like lambda, so you only pay for usage

skj 7y ago
GCR is the container registry and does nothing but store your artifacts.
- PhilippGille 7y ago
  The article and comments are about Google Cloud Run

anirudhgarg 7y ago

I don't think you can scale up and scale down Fargate based on Http requests

staticassertion 7y ago
I'm not sure if you can reasonably scale to 0, but I believe you can attach Autoscaling Groups to Fargate.
- anirudhgarg 7y ago
  Most likely it would be based on CPU/Memory and not requests
  - reilly3000 7y ago
    Most definitely, but you can auto scale on custom metrics with a bit of glue. Even a very small node app has a start time in the 10-30 sec range. Every auto scaling system, even cloud run, can struggle to keep up with extremely bursty traffic. If you want no timeouts, you have to overprovision.

asdfasdfgdy 7y ago

Disclaimer: I work on cloud run Another advantage not stated by others is that cloud run (mostly) adheres to the KNative API spec. This allows you lift-and-shift your application from cloud run to a Kubernetes cluster with the KNative plugin installed, a feature you can’t find with any other serverless product

ignoramous 7y ago
Thanks. What are the usual cold start and warm start times for Cloud Run? Is there potential for those start times to go down to a few milliseconds in the near-future?