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

Matt's analogy

“The kitchen and storage rooms nobody sees but everyone relies on for the meal. ”

A line-drawn illustration for Back-end.

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

Job guide

Add a Database

When your app needs to save stuff, you need a database

Job guide

Add Authentication

When you need users to log in, stay logged in, and recover access later.

Tool review

Cloudflare Turnstile

Cloudflare’s CAPTCHA replacement for lightweight human verification on forms, signups, and other abuse-prone flows. A low-friction way to make cheap bot abuse harder without making real users solve puzzle garbage all day.

Tool review

Convex

Backend platform for apps where data changes should update the UI automatically, without building a lot of custom realtime wiring. Includes a database, server functions, realtime updates, auth integrations, file storage, search, crons, and AI-agent workflow tools.

Comparison

Supabase vs Firebase for Vibe Coders

These are two of the fastest ways to bolt a real backend onto an AI-built app, but they optimize for different futures. Supabase is usually the cleaner default for SQL-first web apps. Firebase is still brutally effective when mobile support, post-launch tooling, and the wider Google app ecosystem matter most—and it now has a real Postgres path through SQL Connect.

Blog post

The 7 Best Claude Design Alternatives in 2026

Claude Design is impressive, but it shares usage limits with the rest of Claude. These alternatives are better fits for free UI exploration, Figma workflows, production code, full apps, and presentations.

Related tool or page

collection

Add a Database

Most real backend work starts once you need structured data and server-side logic.

Related glossary terms

Migration

Migrations are how teams change a database safely over time instead of poking production tables by hand and hoping for the best.

Shared tags: backend

Schema

A schema says what fields exist, what types they should be, and sometimes what counts as valid data.

Shared tags: backend

SQL

SQL is how you ask a relational database for exactly the rows you want, change stored data, or define tables and relationships.

Shared tags: backend