Backend Engineering
Against a real PostgreSQL and a real HTTP boundary, you connect data integrity, idempotency, resource authorization, observability, deployment, and incident review into one backend system you can verify.
코스
- Production Backend API Capstone — From PostgreSQL and real HTTP to operational evidence, proven as one system
- Concurrency — When Two People Touch One Row — Stock goes negative because of ordering, not code
- Idempotency — Two Clicks, One Charge — You cannot stop the retry. You can only stop the duplicate
- I renumbered a field and the old client silently read the wrong value — Verify protobuf bytes and schema-evolution rules by hand