Memory hook: Bound the call; follow the trace.
Must remember
- Use supported client libraries, REST or gRPC with an enabled API, correct project, service identity and quota. Paginate large result sets, request only necessary fields, batch supported work and cache safe responses.
- Handle transient errors with bounded exponential backoff and jitter. Respect retry guidance; do not blindly retry non-idempotent writes or permanent permission failures.
- Manage database pools and transaction boundaries explicitly. Acknowledge messages after successful durable processing; design deduplication and dead-letter handling for repeated failures.
- Log structured request identifiers, outcomes and safe diagnostic context. Propagate trace context across HTTP and messaging boundaries so spans can reveal the slow dependency.
- Cloud Logging explains events, Monitoring quantifies behavior, Trace follows request latency and Error Reporting groups failures. Correlate them instead of selecting a tool solely by product name.
- Measure user-relevant latency/error SLOs and dependency saturation. AI-assisted diagnostics can suggest hypotheses, but validate them against telemetry and controlled changes.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| A request is slow across several services | Distributed traces correlated with logs and dependency metrics. |
| API returns a transient quota-related failure | Inspect quotas and rate, then apply bounded retry/backoff when appropriate. |
Traps
- Retrying a denied request repeatedly does not fix IAM.
- Logging full request bodies can expose secrets or personal data.
Active recall
1. Why use pagination?
To process bounded responses without losing records or exhausting memory.
2. When acknowledge a message?
After the intended durable processing succeeds, according to the delivery contract.
3. What does jitter prevent?
Many clients retrying simultaneously and creating another traffic spike.
4. What does a trace ID connect?
Spans and related logs belonging to an end-to-end request or operation.
5. Why monitor dependencies separately?
An application symptom may originate in a database, API quota or downstream service.