Thuta Learning
BasicWeb Developmentbeginner

Website, Web App, and Web vs Internet

What you'll walk away with

  • Explain the core ideas behind Website, Web App, and Web vs Internet
  • Read the diagram and trace how a request, piece of data, or event flows through the system
  • Explain how this piece connects into the larger web architecture picture

Build the mental model

Many people treat "Web" and "Internet" as synonyms, but they aren't the same thing. The Internet is the underlying network infrastructure, and the Web is just one service running on top of it.

  • Web — the system of browsing pages and resources through a browser
  • Email — sending/receiving messages between mail servers
  • Messaging — real-time chat and instant messaging services
  • File transfer — moving files directly between systems
  • Online games — game clients talking directly to game servers

A website is a collection of pages and resources accessible through a browser, usually centered on content. A web application leans more interactive, working with user accounts, state, and actions.

  • Closer to "website" — blog, documentation site, online store
  • Closer to "web application" — dashboard, SaaS product, social network

Not a strict boundary

An online store itself can drift toward web-application territory once login, a cart, and checkout enter the picture.

A static site serves prebuilt files exactly as written. A dynamic site generates or fetches content on the fly, based on the user, database, the request itself, or auth state.

text
INTERNET vs WEB, STATIC vs DYNAMIC
----------------------------------
INTERNET (the network)
  |-- Web (browser + pages/resources)
  |-- Email
  |-- Messaging
  |-- File transfer
  `-- Online games

STATIC              DYNAMIC
Browser             Browser
  |                   |
  v                   v
Static Files        Server
(same every time)      |
                        v
                    App Logic
                        |
                        v
                    Database

Connect it to a real scenario

The code example takes an object describing a site and classifies it two separate ways: website-like versus web-application-like, and static versus dynamic.

ExampleResult
Personal blogwebsite + static
News sitewebsite + dynamic (pulls from a database, but no accounts)
Analytics dashboardweb application + dynamic

Two independent judgments

Nothing forces a website to be static or a web application to be dynamic — a news site proves a website can be dynamic while still reading as content-first.

Try the working example

javascript
function classifySite(site) {
  const { hasUserAccounts, hasDatabase, contentChangesPerUser } = site;

  const interactivityScore =
    (hasUserAccounts ? 1 : 0) +
    (hasDatabase ? 1 : 0) +
    (contentChangesPerUser ? 1 : 0);

  const nature = interactivityScore >= 2 ? "web application" : "website";
  const behavior =
    hasDatabase || contentChangesPerUser ? "dynamic" : "static";

  return { nature, behavior };
}

const personalBlog = {
  hasUserAccounts: false,
  hasDatabase: false,
  contentChangesPerUser: false,
};

const newsSite = {
  hasUserAccounts: false,
  hasDatabase: true,
  contentChangesPerUser: false,
};

const dashboardApp = {
  hasUserAccounts: true,
  hasDatabase: true,
  contentChangesPerUser: true,
};

for (const [name, site] of [
  ["Personal blog (hand-written HTML)", personalBlog],
  ["News site (loads articles from a database)", newsSite],
  ["Analytics dashboard (per-user data)", dashboardApp],
]) {
  const result = classifySite(site);
  console.log(`${name} -> ${result.nature}, ${result.behavior}`);
}
You should see
Personal blog (hand-written HTML) -> website, static
News site (loads articles from a database) -> website, dynamic
Analytics dashboard (per-user data) -> web application, dynamic

5-minute try-it

Create a site object for an e-commerce store with hasUserAccounts: true, hasDatabase: true, contentChangesPerUser: false (accounts exist, but product pages look the same for everyone). Predict the output before running it.

One important caution

Treating "Internet" and "Web" as interchangeable, forgetting email, messaging, and other services use the Internet without being the Web

Treating website vs web application as a strict either/or category, when it's really a spectrum

Wikipedia — World Wide WebHow the Web Works

Easy traps

  • Treating "Internet" and "Web" as interchangeable, forgetting email, messaging, and other services use the Internet without being the Web
  • Treating website vs web application as a strict either/or category, when it's really a spectrum
  • This course is a system map, not a deep-dive on every piece -- for depth on REST, DNS/hosting, databases, or security, continue to the API Tutorial, Cloud & Deployment, SQL, or Cybersecurity tutorials.

Exercise

Create a site object for an e-commerce store with hasUserAccounts: true, hasDatabase: true, contentChangesPerUser: false (accounts exist, but product pages look the same for everyone). Predict the output before running it.

You'll know it worked when: Personal blog (hand-written HTML) -> website, static News site (loads articles from a database) -> website, dynamic Analytics dashboard (per-user data) -> web application, dynamic