Glossary Term App Architecture

Back-end

The behind-the-scenes part of an app that handles data, business logic, authentication, payments, and anything the browser should not do by itself.

#backend #server #architecture

When this matters

Backend work matters as soon as your app has real users, protected data, private API keys, or actions that should not trust the browser. Contact forms, payments, dashboards, login flows, and webhooks all push you into backend territory fast.

Small example

Charging a credit card belongs on the backend because the secret API key and the final amount should be controlled server-side, not trusted from the browser.

Frontend: collect form data and send it to /api/checkout
Backend: validate the order, call Stripe, return success or failure

Common mistake or lookout

Assuming a frontend framework automatically makes security decisions for you. If sensitive logic runs in the browser, users can inspect it, bypass it, or call your APIs directly.

Why this matters for vibe coders

Vibe coders can get surprisingly far with polished frontends, then hit a wall when they need sessions, server validation, or anything secret. Knowing what belongs on the backend keeps you from forcing the browser to do work it should never be trusted with.

Where this shows up on the site

Related tool or page

Related glossary terms