Frontend & Backend

Every app has a front of house and a back of house. Same as a restaurant.

The frontend is everything you can see and touch. Pull up Amazon, or honestly any website you use. The menu bar, the buttons, the search box, the little "Add to Cart" that turns green when you click it. All of it is just a list of things you're allowed to ask for. That's the dining room. The menu, the host stand, the table you're sitting at.

But here's the part that trips people up: nothing on that menu is actually happening at your table.

When you hit "Buy Now," it's like handing your order to a waiter. He doesn't cook it in front of you. He walks it back, the kitchen does the real work, and he carries the result back out to you.

That kitchen is the backend. The database, the business logic, the server. The stuff you never see.

Anything heavy happens back there, out of sight:

• Pulling up your entire order history
• Charging your credit card
• Checking whether that coupon code is real
• Firing off the confirmation email

The frontend only handles what fits at the table: how the buttons look, what color the page is, the small animations when you hover. It's the experience. The backend is the work.

Think Michelin star. They're not torching your steak tableside for show. They need the walk-in fridge, the grill, the prep station, the sous chef sweating in the back. Software is exactly the same. The interesting work needs the full kitchen, and you're not meant to see it.

Here's the fastest way to tell which one just broke.

A frontend problem is the one you've seen a hundred times. A button that won't click. Text piled on top of an image. A page that looks fine on your laptop and completely falls apart on your phone. The dining room's a mess, but the kitchen is still cooking. Annoying, usually quick to fix.

A backend problem is bigger and scarier. When a service like Cloudflare or AWS goes down and takes half the internet with it, that's the backend. The shared kitchen caught fire, and every restaurant that was quietly relying on it goes dark at the same time. You'll see a dozen apps break at once and none of them are actually the ones at fault.

So next time something's off, ask yourself: is the dining room messy, or is the kitchen on fire? You'll almost always know which.

The frontend is what you experience. The backend is what actually happens.