Module 4 of 6Lesson 2 of 2~12 min
Behind the API, data, files and third-party services
A feature that looks simple can depend on a database, file storage and several third-party services. This lesson helps you see what sits behind an API and decide what must happen during the request and what can run in the background, for faster screens and better-controlled failures.
Lesson objective
By the end of this lesson, you will be able to describe what sits behind an API (database, file storage, third-party services, background jobs, logs) and choose, for a feature, what must happen during the request and what can happen in the background.
Topics covered
- backend
- database
- third-party services
- background jobs
- file storage
Where it fits
From frontend to database
Who does what in a web product, and where must each rule run?
Lessons in this module
- Frontend, backend and API, who does what
- Behind the API, data, files and third-party services (this lesson)
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.
Related courses
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Git for PMs: ship as a team without putting production at risk
3 hr 30 min
- Tech for PMsJuniorSome basics are useful: introductory knowledge of the topic.
Design and test an API integration as a PM
3 hr
- Tech for PMsJuniorSome basics are useful: introductory knowledge of the topic.
Model your product’s data and query it with SQL
3 hr 30 min