Tech Stack Impact Explorer

How a Click Gets There

  • DNS helps your browser find the server hosting the website. HTTPS carries the message. CRUD is what the database does when the message arrives. Three words that already show up on every other page — named simply here.

How your browser interacts with a company’s database

You do not click a database. You type a webpage URL in the browser — or search, then click the URL in the results. Once you are on the page, you click a button, a menu, a heart, a comment. Underneath, three different systems take a turn: a phone book (DNS), a locked envelope (HTTPS), and four verbs in storage (CRUD).

This is not a networking course. It is just enough so the pictures on Welcome, Tech Stack Basics, and Popular tech stack options have names.

What happens after you click

After you type a URL — or click a button, a heart, a menu — your browser still has to do three jobs before anything on the screen can change.

01 · Find the website

DNS = Domain Name System

Your browser cannot guess which machine on the internet is hosting the website or software you want. DNS looks up the name (duckbuddy.net) and returns the address of that server — then the browser can ask it for the pages.

Ex: https://duckbuddy.net/people?hobby=hiking — DNS only looks up duckbuddy.net, the name of the site, to find the server hosting DuckBuddy. The rest of the address (/people?hobby=hiking) is not DNS.
02 · A private request

HTTPS = Hypertext Transfer Protocol Secure

Every request your browser sends across the internet uses a locked, secure form of communication. That is how you get back what you wanted to see — and strangers on the path cannot read it.

The S means the conversation is private.

Ex: https://duckbuddy.net/people?hobby=hiking — the https:// lock and this whole address are a private GET request from your browser: “show me people who like hiking.”
03 · Add, get, edit, or remove

CRUD = Create, Read, Update, Delete

When that request reaches the company’s database, it always does one of a few standard actions: add, get, edit, or remove — based on what you clicked in the browser.

This usually stays inside the company, not on the public internet.

Ex: https://duckbuddy.net/people?hobby=hiking — the database Reads (looks up) people whose hobby is hiking. This click does not Create, Update, or Delete.

In other words: DNS helps your browser find the server hosting the site, a private request is sent, then the database adds, gets, edits, or removes — based on what you clicked.

DNS — the phone book

DNS is what helps your browser find the server on the internet that is hosting the website or software you want to use. You type a name people can read; DNS turns that name into the address of that hosting server.

Ex: the phone book your computer asks
google.com→an address for Google’s servers
duckbuddy.net→the server hosting DuckBuddy’s website
apicallexplorer.lovable.app→an address for this learning series
01 · What it is

A lookup, not the website

You type duckbuddy.net. Your browser asks DNS: “Which server on the internet is hosting that website?” DNS answers with that server’s address. Only then can the browser send HTTPS there.

If DNS is wrong or down, the page never loads — not because DuckBuddy’s screens are broken, but because your browser cannot find the hosting server.

Where it sits: not on DuckBuddy’s laptop, and not in PostgreSQL. It is a public lookup service on the internet. Your internet provider and others keep copies so the answer is fast.
02 · When it happens

Mostly when you first visit

Opening duckbuddy.net needs DNS — that is how the browser finds the server hosting DuckBuddy. Clicking Connect on Sofia usually does not ask DNS again — your browser already knows which hosting server it is talking to.

Think of DNS as finding the building that hosts the site. HTTPS is walking in and speaking. CRUD is what the filing cabinet inside does.

You don’t program DNS when you add a Connect button. Someone at the company points the name at the servers once. Feature work almost never “changes DNS.”

HTTPS — the locked envelope

Once DNS has found the server hosting the site, your browser and the service layer send messages across the public internet. HTTPS is those messages, with a lock on them.

Your browser

Sends a request: “GET the hiking people” or “POST a new connection to Sofia.” This is the front-end’s HTTPS call from your computer.

HTTPS public internet

The service layer

Receives it on company servers, decides what is allowed, talks to the database, then sends a response back in another locked envelope.

The S

The lock

HTTP would send the same message with no lock — anyone on the path could read it. HTTPS encrypts it. That is why the address bar shows a lock, and why passwords and bank rows travel this way.

You don’t need the math. Remember: S = private on the public internet.
Ex: two common methods

GET and POST

GET Ask for something. Filter Texas. Open a post. Play a title. POST Send something new. Add to cart. Connect. Like. Turn a Zap on.

There are others (PUT, PATCH, DELETE). For this series, GET ≈ “show me” and POST ≈ “save this” is enough.

What it is not

Not the database call

HTTPS stops at the service layer. The service then talks to PostgreSQL or Redis on a private network inside the company. Your browser never HTTPS-es the database.

That is the lock on the door from Tech Stack Basics: the envelope is public; the filing cabinet is not.

The API Calls Explorer goes deeper on types of calls. Here, HTTPS only means: the locked message between your computer and the service.

CRUD — four things a database can do

After HTTPS arrives, the service asks the database to change (or not change) data. Those asks are always one of the actions below.

C

Createadd a row

Make something that was not there. Ex: Add to cart. Connect with Sofia. Tap Like (your like row). Book a room.

R

Readlook it up

Look without changing. Ex: Travel posts on a blog. Customers in Texas. Checking transactions. Open a Figma file.

U

Updatechange a row

Change something that already exists. Ex: Turn a Zap on. Bump a like count. Save your place in a video. Edit a phone number.

D

Deleteremove a row

Take it out. Ex: Unlike a post. Remove an item from the cart. Banks almost never Delete money rows — they Create a reversing one instead.

HTTPS method ≠ CRUD letter

They often line up — GET with Read, POST with Create — but they are not the same system. HTTPS is the envelope on the public internet. CRUD is the verb inside the database. One POST can Create a like and Update a count.

You don’t write CRUD in the browser

The front-end never says “Read Texas” to PostgreSQL. It sends HTTPS to the service. The service is the only thing allowed to speak CRUD. That is why a feature can need a new button, a new HTTPS route, and a new column.

Where CRUD sits: on the company’s database machines in the cloud — the same place as Tech Stack Basics. Not on your laptop.

Put it all together

Follow the same DuckBuddy example through all seven steps: open the people page or choose Hiking to see people who like hiking. https://duckbuddy.net/people?hobby=hiking

  1. 1

    Browser / front end

    You open the hiking people page

    You open DuckBuddy’s people page or choose Hiking in the hobby filter. The front end starts a request to show people who like hiking.

    Ex: https://duckbuddy.net/people?hobby=hiking — the address bar, hobby filter, and profile cards.

  2. 2

    DNS & HTTPS

    The browser finds the website

    DNS finds an address for the server hosting duckbuddy.net. The browser creates an encrypted HTTPS connection and sends a GET request for the hiking people page.

    Ex: DNS looks up only duckbuddy.net — not /people?hobby=hiking. The HTTPS request carries the path and hobby filter.

  3. 3

    Web server & API

    The server receives the request

    DuckBuddy’s server recognizes the /people path and passes the hiking filter to the program that handles people searches.

    Ex: GET /people?hobby=hiking arrives at company servers — not directly at PostgreSQL.

  4. 4

    Service layer

    The service checks access and asks for hikers

    DuckBuddy’s Python program identifies the signed-in person, checks which profiles they may see, and asks the database for people whose hobby is hiking.

    Ex: The service asks for visible hiking profiles, including the name, hobby, and location needed by the profile cards.

  5. 5

    Database / CRUD: Read

    The database reads matching people

    The database looks up people whose hobby is hiking and returns the matching records to the service. This click reads existing data; it does not add, edit, or remove records.

    Ex: Anna, hiking, Austin — an illustrative matching row. This request uses Read, not Create, Update, or Delete.

  6. 6

    HTTPS response

    The response travels back

    The service packages the matching profiles and sends an encrypted HTTPS response back to the browser, with a status code telling it whether the request succeeded.

    Ex: The return path is database → service layer → HTTPS response, carrying hiking profiles such as Anna in Austin.

  7. 7

    Front end

    The browser displays the hiking people

    The front end updates the profile cards with the returned hiking people. Anna’s name, hiking hobby, and Austin location appear on the screen without the browser talking to the database.

    Ex: The hiking people list at https://duckbuddy.net/people?hobby=hiking now displays the matching profiles.

Then it comes back: database → service layer → HTTPS response → front end updates the screen. Not every request repeats every step: DNS answers and connections can be reused, cached results may avoid a fresh database query, and some pages do not need a database.

Where to Go Next

Keep going in order, or jump to any page from the top menu.