Learning on Web Dev Open is free for all.

Backend Engineering > Proving it works, then shipping itThe API behind something real
Phase 05Proving it works, then shipping it279 of 434

The API behind something real

A service with persistence, validation, an error contract and a front end that handles every state, deployed, with a README somebody could follow.

Solo project180 minAI pair

Done when

  • At least five endpoints across more than one resource, live on a URL
  • Every request body validated at the boundary, with field-level errors
  • One error envelope used everywhere, including for unhandled exceptions
  • A front end with distinct loading, empty and error states for each call
  • Indexes for every query the application actually runs
  • A README with the contract, the data model, and one tradeoff you made and why

Nobody marks this for you. It goes into your phase checkpoint, where a person does.

You should now be able to

  • Ship a documented API to a live URL
  • Handle every failure the contract names
  • Defend your data model in writing
Ask the community

Loading…

← PreviousLogs you can read, and a rollback you have rehearsedProving it works, then shipping itNext →Auth, and something worth protectingProving it works, then shipping it