REST API & Backend Engineering
Auth, pagination, idempotency, and the 14 ways a naive CRUD API fails in production. The track job posts actually filter on.
Mastery unlocks after a 90% Quiz score
Real-world analogy
A backend is a restaurant kitchen. The menu is the API. The ticket system is the queue. If the kitchen has no tickets, every waiter shouts at the chef.
◎ Why it matters in production
Timeouts, retries, and dual-writes are how outages start. Interviewers ask you to design an API because it reveals whether you've felt these failures — or only read about them.
Fundamental concepts you will master
Resources, not verbs
Nouns, status codes, and why POST /deleteUser is a design smell.
AuthN vs AuthZ
JWTs, sessions, refresh tokens, and the difference between who you are and what you may do.
Idempotency
The payment was charged twice. Here's the header that would have stopped it.
N+1 and pagination
Cursor vs offset, and why page 50 of offset pagination lies to you.
Step-by-step curriculum
HTTP as a contract
Methods, status codes, headers, and content negotiation.
CRUD that survives
Validation, error shapes, pagination, filtering.
Auth in practice
Password hashing, JWT, refresh rotation, RBAC.
Data layer
Transactions, isolation, migrations, and the ORM footguns.
Production shape
Logging, metrics, tracing, rate limits, and graceful shutdown.
Ready to see it in action?
Build your own path, step through operations, and watch mastery unlock after 90%.
Pointer Phantom
Direct Byte Access
+1,250 XP → Cache Ghost