/Go Engineering/Phase 9

Phase 9Days 41-45

Production Go Services

Architecture, Redis, background work, gRPC, observability, and reliability

Phase Goal

Design services that remain understandable under load, failure, and team growth.

Progress

Notes

Open the written lectures for this course before checking off the phase topics.

Projects

Watershed Telemetry Pipeline

Day 41: Service Architecture & Dependency Wiring

Define cmd/internal server layout in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when cmd/internal server layout is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for cmd/internal server layout and fix it deliberately

Define Transport, service, repository, and domain boundaries in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Transport, service, repository, and domain boundaries is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Transport, service, repository, and domain boundaries and fix it deliberately

Define Explicit constructor injection in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Explicit constructor injection is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Explicit constructor injection and fix it deliberately

Define Configuration validation and startup failure in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Configuration validation and startup failure is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Configuration validation and startup failure and fix it deliberately

Day 42: Redis, Caching & Distributed Coordination

Define Cache-aside, TTL, invalidation, and stampedes in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Cache-aside, TTL, invalidation, and stampedes is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Cache-aside, TTL, invalidation, and stampedes and fix it deliberately

Define Rate limiting and atomic Redis operations in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Rate limiting and atomic Redis operations is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Rate limiting and atomic Redis operations and fix it deliberately

Define Distributed locks and when not to use them in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Distributed locks and when not to use them is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Distributed locks and when not to use them and fix it deliberately

Define Failure policy when Redis is unavailable in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Failure policy when Redis is unavailable is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Failure policy when Redis is unavailable and fix it deliberately

Day 43: Background Jobs & Reliable Events

Define Queue ownership, retries, backoff, and dead letters in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Queue ownership, retries, backoff, and dead letters is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Queue ownership, retries, backoff, and dead letters and fix it deliberately

Define Idempotent consumers and outbox pattern in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Idempotent consumers and outbox pattern is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Idempotent consumers and outbox pattern and fix it deliberately

Define At-least-once delivery consequences in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when At-least-once delivery consequences is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for At-least-once delivery consequences and fix it deliberately

Define Graceful worker shutdown and observability in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Graceful worker shutdown and observability is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Graceful worker shutdown and observability and fix it deliberately

Day 44: gRPC, Metrics, Traces & SLOs

Define Protobuf contracts and gRPC boundaries in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Protobuf contracts and gRPC boundaries is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Protobuf contracts and gRPC boundaries and fix it deliberately

Define Unary interceptors, deadlines, and status errors in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Unary interceptors, deadlines, and status errors is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Unary interceptors, deadlines, and status errors and fix it deliberately

Define Metrics cardinality, structured logs, and traces in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Metrics cardinality, structured logs, and traces is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Metrics cardinality, structured logs, and traces and fix it deliberately

Define SLIs, SLOs, alerts, and operational runbooks in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when SLIs, SLOs, alerts, and operational runbooks is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for SLIs, SLOs, alerts, and operational runbooks and fix it deliberately

Day 45: Mini Project — Watershed Telemetry Pipeline

Define Burst-heavy station ingestion and validation service in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Burst-heavy station ingestion and validation service is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Burst-heavy station ingestion and validation service and fix it deliberately

Define PostgreSQL source of truth plus Redis latest-reading cache in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when PostgreSQL source of truth plus Redis latest-reading cache is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for PostgreSQL source of truth plus Redis latest-reading cache and fix it deliberately

Define Background alert evaluation and idempotent events in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Background alert evaluation and idempotent events is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Background alert evaluation and idempotent events and fix it deliberately

Define Project requirements, load test, metrics, and runbook in plain language and explain the problem it solvesTrace what the Go compiler or runtime does when Project requirements, load test, metrics, and runbook is usedWrite a tiny example, then apply it to a realistic backend taskDiagnose the beginner failure mode for Project requirements, load test, metrics, and runbook and fix it deliberately

Capstone

Watershed Telemetry Pipeline

Ingest field-station readings, deduplicate retransmissions, update latest-value views, and emit threshold alerts that survive worker restarts and Redis outages.

Sustained ingest target with bounded queue growth
Duplicate readings never create duplicate alerts
SLO dashboard and dependency-failure runbook

Phase Complete!

After this phase, you'll be able to:

cmd/internal server layout
Transport, service, repository, and domain boundaries
Explicit constructor injection
Configuration validation and startup failure
Cache-aside, TTL, invalidation, and stampedes
Rate limiting and atomic Redis operations
Distributed locks and when not to use them
Failure policy when Redis is unavailable

You can apply Phase 9 skills in a finished, explainable Go project.

Back to all phases

Phase Goal

Day 41: Service Architecture & Dependency Wiring

cmd/internal server layout

Transport, service, repository, and domain boundaries

Explicit constructor injection

Configuration validation and startup failure

Day 42: Redis, Caching & Distributed Coordination

Cache-aside, TTL, invalidation, and stampedes

Rate limiting and atomic Redis operations

Distributed locks and when not to use them

Failure policy when Redis is unavailable

Day 43: Background Jobs & Reliable Events

Queue ownership, retries, backoff, and dead letters

Idempotent consumers and outbox pattern

At-least-once delivery consequences

Graceful worker shutdown and observability

Day 44: gRPC, Metrics, Traces & SLOs

Protobuf contracts and gRPC boundaries

Unary interceptors, deadlines, and status errors

Metrics cardinality, structured logs, and traces

SLIs, SLOs, alerts, and operational runbooks

Day 45: Mini Project — Watershed Telemetry Pipeline

Burst-heavy station ingestion and validation service

PostgreSQL source of truth plus Redis latest-reading cache

Background alert evaluation and idempotent events

Project requirements, constraints & review

Watershed Telemetry Pipeline

Phase Complete!