Production Engineering

A feature is not finished when it appears on a screen. It is finished when retries, partial failure, data changes, delivery, and incident recovery keep the same meaning. This course applies production principles to example service boundaries and turns them into evidence shared by product, design, engineering, users, and operations.

What you will be able to do

turn requirements into success, in-progress, partial-failure, and failure states
separate HTTP retry keys from request correlation IDs
design tables, indexes, and pools from real queries and time budgets
define Timeout, Unknown, Retry, and Reconcile boundaries for providers, Kafka, AI, and notifications
verify authentication, authorization, audit, and upload integrity together
make RAG source, search copies, permissions, and quality converge
operate expand/contract migrations, SHA images, readiness, smoke, and rollback
close completion with bounded RED metrics, tests, and SLO evidence
connect partial failure, recovery, and static-client boundaries into cross-service evidence
operate protobuf gRPC contracts and WebRTC signaling/media boundaries behind a cost guard

The flow

[1] requirement ─▶ [2] HTTP ─▶ [3] database ─▶ [4] external failure
       │                                      │
       ▼                                      ▼
[12] capstone ◀─ [11] observability ◀─ [10] Compose ◀─ [9] release
                                  ▲
                 [5] auth ─▶ [6] files ─▶ [7] AI/RAG ─▶ [8] migrations

Steps

Turn requirements into states and evidence
Fix HTTP retries and request correlation
Design tables, indexes, and pools from query budgets
Handle Timeout, Unknown, Retry, and Reconcile
Make authentication, authorization, and audit one boundary
Validate uploads and publish them atomically
Bind AI providers and RAG to permission and quality
Change schemas with expand/contract and idempotent backfills
Bind a verified commit to a release and image
Operate Compose, readiness, reverse proxy, and rollback
Follow one request with RED, correlation, and SLOs
Verify a change with five perspectives and deployment smoke
Close cross-service partial failure, recovery, and platform boundaries
Introduce gRPC and WebRTC behind an explicit cost guard

Prerequisites: experience with architecture-patterns, data-engineering-postgres, or quality-and-testing, plus basic PostgreSQL and HTTP.

Production Engineering

What you will be able to do

turn requirements into success, in-progress, partial-failure, and failure states
separate HTTP retry keys from request correlation IDs
design tables, indexes, and pools from real queries and time budgets
define Timeout, Unknown, Retry, and Reconcile boundaries for providers, Kafka, AI, and notifications
verify authentication, authorization, audit, and upload integrity together
make RAG source, search copies, permissions, and quality converge
operate expand/contract migrations, SHA images, readiness, smoke, and rollback
close completion with bounded RED metrics, tests, and SLO evidence
connect partial failure, recovery, and static-client boundaries into cross-service evidence
operate protobuf gRPC contracts and WebRTC signaling/media boundaries behind a cost guard

The flow

[1] requirement ─▶ [2] HTTP ─▶ [3] database ─▶ [4] external failure
       │                                      │
       ▼                                      ▼
[12] capstone ◀─ [11] observability ◀─ [10] Compose ◀─ [9] release
                                  ▲
                 [5] auth ─▶ [6] files ─▶ [7] AI/RAG ─▶ [8] migrations

Steps

Turn requirements into states and evidence
Fix HTTP retries and request correlation
Design tables, indexes, and pools from query budgets
Handle Timeout, Unknown, Retry, and Reconcile
Make authentication, authorization, and audit one boundary
Validate uploads and publish them atomically
Bind AI providers and RAG to permission and quality
Change schemas with expand/contract and idempotent backfills
Bind a verified commit to a release and image
Operate Compose, readiness, reverse proxy, and rollback
Follow one request with RED, correlation, and SLOs
Verify a change with five perspectives and deployment smoke
Close cross-service partial failure, recovery, and platform boundaries
Introduce gRPC and WebRTC behind an explicit cost guard

Prerequisites: experience with architecture-patterns, data-engineering-postgres, or quality-and-testing, plus basic PostgreSQL and HTTP.

Production Engineering — Boundaries, Performance, Recovery, and Delivery in 14 Steps

Production Engineering

What you will be able to do

The flow

Steps

Lessons

Step 1 — Turn requirements into states and evidence

Step 2 — Fix HTTP retries and request correlation

Step 3 — Design tables, indexes, and pools from query budgets

Step 4 — Handle Timeout, Unknown, Retry, and Reconcile

Step 5 — Make authentication, authorization, and audit one boundary

Step 6 — Validate uploads and publish them atomically

Step 7 — Bind AI providers and RAG to permission and quality

Step 8 — Change schemas with expand/contract and idempotent backfills

Step 9 — Bind a verified commit to a release and image

Step 10 — Operate Compose, readiness, reverse proxy, and rollback

Step 11 — Follow one request with RED, correlation, and SLOs

Step 12 — Verify a change with five perspectives and deployment smoke

Step 13 — Close partial failure and recovery as a cross-service contract

Step 14 — Close gRPC and WebRTC boundaries with cost guards

Production Engineering — Boundaries, Performance, Recovery, and Delivery in 14 Steps

Production Engineering

What you will be able to do

The flow

Steps

Lessons

Step 1 — Turn requirements into states and evidence

Step 2 — Fix HTTP retries and request correlation

Step 3 — Design tables, indexes, and pools from query budgets

Step 4 — Handle Timeout, Unknown, Retry, and Reconcile

Step 5 — Make authentication, authorization, and audit one boundary

Step 6 — Validate uploads and publish them atomically

Step 7 — Bind AI providers and RAG to permission and quality

Step 8 — Change schemas with expand/contract and idempotent backfills

Step 9 — Bind a verified commit to a release and image

Step 10 — Operate Compose, readiness, reverse proxy, and rollback

Step 11 — Follow one request with RED, correlation, and SLOs

Step 12 — Verify a change with five perspectives and deployment smoke

Step 13 — Close partial failure and recovery as a cross-service contract

Step 14 — Close gRPC and WebRTC boundaries with cost guards