Compute Flashcards
[Cloud Functions (Cloud Functions)]
Overview
Event-driven serverless functions
[Cloud Functions (Developer Experience)]
How easy is it for developers to get started?
Simplified and intuitive, focusing only on writing code snippets that respond to events.
[Cloud Functions (Cost)]
How is billing done?
Pay only for function’s execution time, metered to the nearest 100 milliseconds.
[Cloud Functions (Scalability)]
How does it handle changes in workload?
Auto-scales up and down in response to events, from zero to planet-scale.
[Cloud Functions (Lock-in)]
Is it tied to a specific platform?
No, uses open-source FaaS framework, compatible with multiple environments including on-premises.
[Cloud Functions (Integration)]
What can it integrate with?
Can connect and extend Google and third-party cloud services through events.
[Cloud Functions (Monitoring)]
How can you observe its behavior?
Offers full observability through Cloud Trace and supports local and disconnected development.
[Cloud Functions (Infrastructure)]
Do you need to manage servers?
No, all underlying infrastructure is managed by Google.
[Cloud Functions (Event Responsiveness)]
What kind of events can trigger the code?
Trigger code from Google Cloud, Firebase, Google Assistant, or via HTTP from any application.
[App Engine (Programming Languages)]
Which languages are supported?
Node.js, Java, Ruby, C#, Go, Python, or PHP.
[App Engine (Management)]
How much infrastructure do you have to manage?
Fully managed, letting you focus solely on code.
[App Engine (Diagnostics)]
What tools are available for monitoring?
Cloud Monitoring, Cloud Logging, and Error Reporting for health and performance monitoring.
[App Engine (Versioning)]
How does it handle different app versions?
Supports hosting different versions for development, test, staging, and production environments.
[App Engine (Security)]
What security features are available?
Firewall rules, managed SSL/TLS certificates at no additional cost.
[App Engine (Service Ecosystem)]
What other services can it integrate with?
Tap into a growing ecosystem of Google Cloud services and developer tools.
[Cloud Run (Programming Languages)]
What languages can you use?
Any language, built-in support for Node.js, Go, Java, Kotlin, Scala, Python, .Net and Docker.
[Cloud Run (Container Support)]
How does it work with containers?
Takes any container images, integrates with Cloud Build, Artifact Registry, Docker.
[Cloud Run (Payment)]
How are you billed?
Pay-per-use, billed to the nearest 100 milliseconds.
[Cloud Run (Developer Experience)]
What tools make development easier?
Command-line and UI for quick deployment, integrates with Cloud Code and Cloud Build.
[Cloud Run (Management)]
How much infrastructure do you have to manage?
Fully managed, no infrastructure to worry about.
[Cloud Run (Concurrency)]
How does it handle multiple requests?
Up to 1,000 concurrent requests per container instance.
[Cloud Run (Autoscaling)]
How does it scale?
Fast autoscaling from zero to N depending on traffic.
[Cloud Run (Redundancy)]
How is data replicated?
Services are regional and replicated across multiple zones.
[Cloud Run (Security)]
What are the security features?
Mount secrets, Binary Authorization, sandboxing, dedicated identities, and permissions.
[Cloud Run (Storage)]
What storage options are available?
Up to 32GiB ephemeral storage, connect to Filestore or Cloud Storage FUSE for persistent storage.
[Cloud Run (Monitoring)]
What monitoring tools are available?
Integrated with Cloud Monitoring, Cloud Logging, Cloud Trace, and Error Reporting.
[Cloud Run (Web Traffic)]
Can it process web traffic?
Exposes services publicly for web requests.
[Cloud Run (Event Processing)]
How does it handle events?
Triggers from Google services, SaaS, and your own apps.
[Cloud Run (Portability)]
How portable is it?
Built on Knative, accepts standard container images for cross-platform portability.
[Cloud Run (Custom Domains)]
Can you use your own domains?
Yes, map your services to your own domains.
[Cloud Run (Networking Protocols)]
What networking protocols does it support?
HTTP/1.*, HTTP/2, WebSockets, or gRPC (unary and streaming).