Cheat sheet: Inside a back end
The 25 terms of this lesson, part by part, with the French word a team in France would use.
1. One click, four steps
- Back endback-end
- the part of a site that runs on a server, such as accounts, data and rules, which visitors never see.
- Requestrequête
- a message that a browser sends to a server to ask for a file or data, or to send it something.
- Routeroute
- an address on the server that handles one kind of request, such as POST /bookings to create a booking.
- Business rulesrègles métier
- the company's decisions written as code, such as who may book, what things cost and what can be cancelled.
- Databasebase de données
- an organised store of data on a server, such as every message left in a guestbook.
- Responseréponse
- the message a server sends back for each request, made of a status code, headers and a body.
2. The route: an address for each job
- Routeroute
- an address on the server that handles one kind of request, such as POST /bookings to create a booking.
- HTTP methodméthode HTTP
- the word at the start of a request that says what kind of action it is, such as GET to read or POST to create.
- Endpointendpoint, point d'accès
- another word for a route: one address of a back end that programs can call.
- Domain namenom de domaine
- the readable name of a website, such as
leboncoin.fr, which its owner rents by the year.
3. The rules: where the business lives
- Business rulesrègles métier
- the company's decisions written as code, such as who may book, what things cost and what can be cancelled.
- Server-side checkvalidation côté serveur
- a check that runs on the company's server, which the visitor cannot see or change.
- Bugbug
- a mistake in code that makes a program do the wrong thing.
4. The answer: a page, or data
- Status codecode de statut, code HTTP
- a three-digit number in each response that says what happened, such as 200 for success or 404 for a missing page.
- JSONJSON
- a plain-text format for data, made of names and values, that any program can read, such as
"price": 12. - Server renderingrendu côté serveur
- a way of building pages where the server creates each page when someone asks for it, with its content inside.
5. An API: one back end for every screen
- APIAPI
- a way for one program to ask another for data or actions, such as a shop asking its stock software what is left.
- JSONJSON
- a plain-text format for data, made of names and values, that any program can read, such as
"price": 12. - Queryparamètres d'URL, query string
- the part of a web address after the
?, which holds details such as the words you searched for. - Headeren-tête, header
- a label in a request or a response that gives details about it, such as the type of file or how long to keep it.
- Documentationdocumentation
- the written guide to a system or a service, which explains how other software can connect to it.
6. What to ask
- Routeroute
- an address on the server that handles one kind of request, such as POST /bookings to create a booking.
- Business rulesrègles métier
- the company's decisions written as code, such as who may book, what things cost and what can be cancelled.
- APIAPI
- a way for one program to ask another for data or actions, such as a shop asking its stock software what is left.
- Documentationdocumentation
- the written guide to a system or a service, which explains how other software can connect to it.
Web Technologies · Back ends · wt.thomasjuldo.com/course/back-ends/inside-a-back-end