6 Q&As for Cloud Run By Me + WE DID GCPUG EXTENDED IN Google Cloud Next SF!

Transcript

1. View Slide

2. Google Cloud Next
   Extendedを開催しましょう…だと！？
   

   View Slide

3. Google Cloud Next SF ‘19
   に殴り込みしたぜ！！！！
   

   View Slide

4. その名も
   

   View Slide

5. View Slide

6. View Slide

7. View Slide

8. 6 Q&As for
   Cloud Run
   By Me
   Kuma Arakawa, SRE, Recruit Lifestyle Co. Ltd.
   

   View Slide

9. ● Previously introduced as “Serverless Containers for Cloud Functions”
   or “GKE serverless add-on” in last year’s Google Cloud Next
   ● Deploy containerized application to either managed or GKE
   environment
   ● Immutable deployment using the concept of “revision”
   ● Knative backend. No vendor lock
   ● Scale from 0
   What is Cloud Run?
   

   View Slide

10. ● As easy as
    gcloud beta run deploy --image [container image]
    or via Web console
    How do you deploy to Cloud Run?
    https://cloud.google.com/run/docs/resource-model
    

    View Slide

11. ● As easy as
    gcloud beta run deploy --image [container image]
    or via Web console
    ● Immutable deployment using the concept of “revision”
    How do you deploy to Cloud Run?
    https://cloud.google.com/run/docs/resource-model
    

    View Slide

12. ● No VPC Access
    ● In roadmap
    VPC Access?
    Cloud
    Memorystore
    Cloud
    Filestore
    Cloud SQL Cloud Load
    Balancing
    Stackdriver
    Cloud
    Storage
    Cloud
    Pub/Sub
    Cloud
    Firestore
    BigQuery
    

    View Slide

13. When to use GCF/Run/GKE ?
    ● GCF: If you can rely on PaaS like
    Cloud Function
    ● Run: When you need to consider
    dependencies, or moving existing
    container applications
    ● GKE: When you need to consider
    network, or your microservice is
    getting complex
    

    View Slide

14. ● Mind startup time
    When scale out, Cloud Run will: retrieve container, start container and
    run entrypoint command to start the server. Seems like no option to
    define the number of minimum up container
    ● Delete temporary files
    Cloud Run disk system uses in-memory filesystem. If you don’t, will get
    out-of-memory error eventually and goes to cold start.
    ● Tune concurrency config
    Concurrency in Run means “serve multiple requests simultaneously”.
    Default is 80 and that is the maximum. Cloud Function has a fixed
    concurrency of 1.
    Any tips to create an app for Cloud Run?
    

    View Slide

15. ● “Streaming HTTP and gRPC support is on our roadmap, but it's still a
    ways out :(“
    ● Invoke API Gateway to do translation from gRPC to JSON
    ● Outbound gRPC/Streaming is support. So you can use Cloud Firestore
    for example.
    gRPC? Streaming HTTP??
    https://news.ycombinator.com/item?id=19616265
    

    View Slide