Member-only story

How To Understand Web Architecture: The Restaurant Analogy

Cameron Manavian
7 min readOct 1, 2019

How does one understand web architecture? If you are a seasoned web developer, you live and breathe it. For newbies or non-techies, here is an analogy to help plan your next byte.

What Does My Lunch Have to Do With Software?

Let’s think of modern web applications as a restaurant. When using the word app in this article, just assume its either a browser application, website, mobile application, or video game with web components.

Obligatory tasty looking food for those that need to go on their lunch break

The reason I use a restaurant is that most people have been in a restaurant, so this analogy should work on 99.9% of the audience that is in a field related to web software engineering.

The last 0.1% — I’m sorry, but I’ll buy you lunch.

Welcome to ServerHut

When initially approaching a restaurant, you are first presented with the sign or logo on the building — very much like the logo you would have on your app, or the URL you’d have for your website. Just like a restaurant, an app has a limited amount of time to make an impression on the visitor, usually about 15 seconds.

Let’s visualize this a little.

Cameron Manavian
Cameron Manavian

Written by Cameron Manavian

Father, Husband, Engineer, CTO, 15+ yrs of software engineering — cameronmanavian.com

Responses (2)

What are your thoughts?

A Google search for “Restaurant analogy” picked up your article. It’s a good presentation of the components involved in web architecture. It also pairs nicely with my own article about how these components can communicate with the REST Architectural…

There are obviously going to be people who will nitpick this analogy but they are the same discontented people that would nitpick anything. I personally believe this article is well done (no pun intended) for it’s purpose.
Clean, clear, bite-sized…