Go Cloud-Native Backend Engineering Bootcamp Certificate

Checkpoint 1: Create an idiomatic Go module with clear package boundaries, interfaces only where they improve substitution, explicit errors and deterministic configuration; enforce gofmt and repeatable builds.
Checkpoint 2: Build a REST/HTTP service with Chi or the standard library, request validation, context propagation, structured error responses and PostgreSQL persistence with versioned migrations.
Checkpoint 3: Implement a background worker using goroutines and channels; bound concurrency, handle cancellation/timeouts and prove the system exits without leaked work.
Checkpoint 4: Add authentication and authorization boundaries plus transaction-safe relational writes; test success, duplicate, invalid-input and dependency-failure paths.
Checkpoint 5: Create table-driven unit/integration tests and run the race detector on concurrent paths; capture a failing test/race scenario, fix it and preserve it as a regression test.
Checkpoint 6: Load-test the API and worker, measure latency/throughput/resource behavior, implement graceful shutdown and document one bottleneck plus the tradeoff used to address it.

Day 1: Choose a real service workflow; define API contract, data model, SLOs, concurrency needs, auth boundary, failure modes and repository/package
Day 2: Implement core domain types, HTTP handlers, validation and error strategy; add PostgreSQL schema/migrations and deterministic local setup.
Day 3: Add authentication/authorization and transactional persistence; write table-driven unit tests and database integration tests for critical behavior.
Day 4: Implement a bounded concurrent worker with goroutines/channels, context cancellation, retries/timeouts and backpressure; exercise cancellation and
Day 5: Run go test -race and fix concurrency defects; add API/worker failure tests, request logging and metrics/traces sufficient to diagnose a bad dependency.
Day 6: Load-test, profile the slowest path, improve one measurable bottleneck, add graceful shutdown and run a database/tool outage or timeout recovery drill.
Day 7: Publish repo, API/data diagrams, migrations, test/race evidence, load-test results, concurrency notes, demo video and an operations/runbook document.