Skip to content
Module
Module 4 of 6Lesson 1 of 2~16 min

Frontend, backend and API, who does what

Putting a business rule in the wrong place creates bugs that are hard to understand and sometimes security holes. This lesson teaches you to split a feature's responsibilities between frontend, API and backend, to read a JSON data exchange and to know which checks must stay on the server.

Updated September 29, 2026.

In short

The frontend is what runs in the user's browser, the backend is what runs on the servers, and the API is the contract that lets them exchange data, often as JSON. For a PM, knowing who does what keeps you from putting a business rule in the wrong place, a common source of bugs and security holes.

Lesson objective

By the end of this lesson, you will be able to split a feature's responsibilities between frontend, API and backend, read a JSON data exchange and justify that a business or security rule is checked on the server side.

Questions this lesson answers

  • What is the difference between frontend, backend and API?

    The frontend displays the interface and reacts to user actions; the backend stores data and applies the rules; the API defines how the two talk to each other.

  • Why should business rules be enforced on the server?

    Because anything that happens in the browser can be changed by the user. A check done only on the client can be bypassed; only the server can be trusted.

  • How do you read a JSON API response?

    JSON organizes data as key-value pairs, with lists in square brackets and objects in curly braces. Find the field names first, then their values and how they are nested.

Topics covered

  • frontend vs backend
  • API
  • JSON
  • business rules
  • technical skills for PMs

In the glossary

Full glossary

Guide on this topic

Where it fits

From frontend to database

Who does what in a web product, and where must each rule run?

Lessons in this module

  1. Frontend, backend and API, who does what (this lesson)
  2. Behind the API, data, files and third-party services

What you will learn in this module

This lesson is part of the course Explain how a web product works, from browser to server

  • Explain how responsibilities are split between browser, frontend, backend, API, database and third-party services, and place where a business rule must run.