What's changed: Created Professional Cloud Developer Chapter 5 (Domain 4 "Integration" part 1: data/storage/messaging = Cloud SQL/Firestore/Cloud Storage connections, connection pool, Cloud SQL Auth Proxy, ADC, Pub/Sub publish/subscribe/at-least-once/dead-letter; consuming Google Cloud APIs = enabling services, client libraries/REST/gRPC, batching/restrict/pagination/caching, exponential backoff, service accounts).
5.1Integrating data, storage, and messaging
Understand managing connections to datastores (Cloud SQL, Firestore, Cloud Storage), reading/writing across data sources, publishing/consuming data with Pub/Sub, and connection security/pooling/auth (e.g., Cloud SQL Auth Proxy).
Apps deliver value by integrating with datastores and messaging, not in isolation. Managing connections securely and efficiently is key.
5.1.1Connecting to datastores
Apps connect to multiple datastores—Cloud SQL, Firestore, Cloud Storage—to read/write. Reuse connections via a connection pool to avoid excessive connections. For secure Cloud SQL connections, use the Cloud SQL Auth Proxy (IAM auth and encryption without exposing a public IP). Authenticate via Application Default Credentials (ADC) and service accounts. Map "secure Cloud SQL connection = Cloud SQL Auth Proxy" and "reuse connections = connection pool."
5.1.2Publishing and consuming via messaging
Pub/Sub is messaging that decouples publishers from subscribers. Publishers send messages to a topic; subscribers receive from a subscription (push/pull). This absorbs spikes, enables async processing, and delivers to multiple subscribers. Design for ordering, duplicates (at-least-once), and dead-letter topics. Map "loosely coupled async delivery = Pub/Sub publish/subscribe."
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.