What it is
When you send a form, book a slot or log in, the frontend passes that to the backend. The backend checks it, saves it in a database, does whatever needs doing, such as taking a payment or sending a confirmation, and sends an answer back.
It runs on a server rather than on your customer's phone, so it can keep private things private, like customer details and payment keys.
An example
On a booking site, the backend knows which slots are free, stops two people booking the same one, saves the booking, takes the deposit through a payment provider, and emails you and your customer.
When you need one
You need a backend when the site has to remember things or act on them:
- Online booking, with availability that updates itself.
- Taking payments or deposits.
- Customer accounts and logins.
- An admin area where you manage enquiries, orders or stock.
- Sending emails or texts automatically.
- Connecting to other systems, like your accounts software or a supplier's stock list.
When you don't
If your site is information plus a way to call or message you, you barely need one. A contact form needs a small backend to send the email, and that's about it.
Who builds it
I build both ends, and I host and look after them, so you deal with one person whether the problem is how a page looks or where the data goes.