Backend Engineering

Read a job posting sentence by sentence to decide what to prepare first, build the missing pieces of a server yourself in Node.js and FastAPI, relearn the CS a service relies on by measuring it, then work through idempotency, locking and gRPC contracts until, against a real PostgreSQL and a real HTTP boundary, data integrity, authorization, observability and deployment come together as one backend system you can verify.

코스

• A Backend Roadmap Read From Job Postings — Decide what to do first, then start
• Node.js Backend — What the Framework Hides — Build what Nest does without installing Nest
• It Wasn't One Request - Everything Got Slow — One request blocks the loop; every request pays
• FastAPI — Types Are the Contract — One misplaced async def stalls the whole server
• CS for Building Good Services — Relearning Textbook Ideas by Measuring — Measure, then choose: data structures, concurrency, caches and clocks
• Idempotency — Two Clicks, One Charge — You cannot stop the retry. You can only stop the duplicate
• Concurrency — When Two People Touch One Row — Stock goes negative because of ordering, not code
• I renumbered a field and the old client silently read the wrong value — Verify protobuf bytes and schema-evolution rules by hand
• Production Backend API Capstone — From PostgreSQL and real HTTP to operational evidence, proven as one system