Backend

When you use an app, you only see a small part of it. You see buttons, texts, and images on your screen. The larger part runs elsewhere: on powerful computers sitting in a company’s data center. This invisible part is called the backend, roughly meaning “back area” or “rear part” in German. That’s where the data lives, where calculations happen, where it’s checked whether your password is correct. The visible part on your device, by contrast, is called the frontend.

Why the work doesn’t happen on your phone

Much of this simply can’t be handled sensibly on a single device. Your chat history should still be there even if your phone breaks. So it isn’t stored only on your device, but centrally. The same goes for your game progress, your messages, or your order history.

A second reason is security. Anything that runs on your device can be read out or altered by someone. That’s why an online shop never checks on your phone whether you have enough money. That decision is made in the backend, outside your reach. As the saying goes: you can’t trust the frontend.

The third reason is computing power. A large AI model needs special chips that cost tens of thousands of euros. Such hardware doesn’t fit in any smartphone. Your question to a chatbot therefore travels to a server, gets answered there, and comes back as text. That’s why many AI services don’t work at all without an internet connection.

Server, database, and the interface in between

A backend usually consists of three building blocks. The server is the computer that runs constantly and waits for requests. The database is a special program that stores information in an organized way and retrieves it quickly. In between lies the actual program code, which decides what should happen for which request.

Frontend and backend talk to each other through an interface, usually called an API. This is a fixed set of questions the frontend is allowed to ask, along with the shape of the answer. You can think of it like a menu. You can order what’s listed, and you get exactly that. You’re not allowed into the kitchen.

A typical sequence: you tap “Log in.” The frontend sends your name and password to a specific address on the backend. There, the password is compared against the stored value. If it matches, a confirmation comes back, and only then does the app show your home screen. This often takes less than half a second.

Backend in outage reports and job postings

The backend is most noticeable when it fails. The app still starts, but nothing loads, or an error message appears. So the frontend is there, but it no longer gets an answer. When a service like Instagram or a banking app goes down worldwide all at once, it’s almost always the backend’s fault.

Job postings distinguish between frontend, backend, and full-stack developers. Backend people work on databases, interfaces, and server logic. Full-stack means someone does both. In news about AI companies, the word often comes up in connection with costs, since servers and electricity are expensive.

A common misconception is that backend and cloud are the same thing. Cloud only describes the fact that the servers belong to and are rented from an outside provider. A backend can just as well sit in your own basement. And one more thing: the backend has nothing to do with whether an app looks good. That’s decided solely by the frontend.