Frontend və backend

Frontend means the front side. It is the part that meets the eye: a heading, a color, a line, a button, and a list. The browser shows these. HTML puts the text, CSS holds the look, and JavaScript changes something when you press. The backend is the back side. A person does not see it on the page. It stands on the server. It checks a password, writes data into a table, and returns an answer. Python, PHP, or Node.js can work there. A simple page can have only a frontend. It keeps nothing, it only shows. Where there is a login, an order, and an account, a backend is needed. A pretty face does not make the back correct by itself. A working back does not make the button visible by itself either.

The frontend shows. The backend keeps and checks. They are the two sides of one button.

• Showing a heading, a color, and a button
• Changing a list when someone presses
• Checking a password and an order on the server
• Writing data into a table and then showing it on the face

With the frontend you fix what a person sees. The place of a word, the color, and the name of a button are here. With the backend you write the rule that is not seen. An empty name is not accepted. The same order is not written twice. The answer comes back to the face and is shown there. The face does not open the back's table by itself. The back does not choose the button's color by itself either. A small notice page can be only a frontend. Where there is a user and money, work without a backend is unsafe, because a person can change a check that stays in the browser.

Drawing one button is easy. The difficulty is tying the button to the rule at the back. When the face is ready, a person thinks the site is finished. If the back does not keep anything, the text can go when you refresh. When the back is ready, a person sees nothing, because there is no face. Mixing both on the same day slows both. First know what the face will show, then write what the back will keep.

The frontend meets the person. Without it the site is an empty window. The backend protects the data. Without it the text only stands for that moment. Not every site needs both. For a notice the face is enough. For a login and an order the back is needed. Learning one does not take the other's place.

The face is seen. The back is not seen. The button is on the face. The check is at the back.

• The frontend is the HTML, CSS, and JavaScript side
• The backend is the work that stays on the server
• Not every page has a backend
• A person can change a check that sits on the face

The face shows the button. The back does not accept the name if it is empty. That is two sides of the same job.

<!-- frontend -->
<button>Göndər</button>

# backend
ad boşdursa, qəbul etmə

• Are frontend and backend the same language? No. The face is often HTML and JavaScript. The back can be Python, PHP, or Node. They are names of a place, not of a language.
• Does every site have a backend? No. A page that only shows can live without a backend. If there is a login and saved data, a backend is needed.
• Does a pretty face finish the site? No. The face is the look. If the data is not kept at the back, the text can go when the page is refreshed.