What you see and click
The front-end
What users see and click on. Built with HTML, CSS, and frameworks like React or Angular. On DuckBuddy, that is React + JavaScript in the browser.
If you have ever wondered — or wanted a simple way to learn about — some of the magic that makes up the functionality of a webpage or online software, this site was made for you.
Every website and app looks like one screen. Underneath, it is layers of technology — a tech stack. Most people only see the user interface. This is a guided tour of those layers: learn the basics, follow a click through DNS, HTTPS, and the database, compare typical company stacks, and explore the code behind clicks and feature requests. Start with Welcome and follow the pages in order, or jump to a topic that interests you.
Here's what's inside:
Think of online software as a finished house. The tech stack is the foundation, materials, and plumbing hidden inside.
A tech stack is the specific combination of programming languages, tools, and databases that developers use to build an application. A typical stack includes:
What you see and click
What users see and click on. Built with HTML, CSS, and frameworks like React or Angular. On DuckBuddy, that is React + JavaScript in the browser.
The work behind the scenes
The server logic that processes data — the layer other pages on this site call the service layer — powered by languages like Python, Java, or Node.js. DuckBuddy's services are Python.
Where information lives
Where user info and files live — MySQL, MongoDB, and others. DuckBuddy uses five, because a profile, a live chat, and a friend suggestion are different kinds of information.
Example
DuckBuddy is a social media networking platform, and this is the stack working behind it. On the left is what the person sees (React + JavaScript). HTTPS calls leave the browser, cross the internet, and land on DuckBuddy's Python servers. Those servers then ask different databases depending on what is on the page. Hover a database on the right to see which part of the screen it is for.
Frontend Developer · Kraków
Hobbies: gaming, hiking
92% match
Online now Redis
Marco: Welcome! Anyone in Madrid?
Anna: Hola from Valencia!
Sofia is typing…
WebSocket HTTPS · Cassandra + RedisMarketing manager, weekend hiker. You both know Anna.
Front-end UI · React + JavaScript — this is the only layer most people ever see
Most companies don't keep everything in one database. They use several — and different kinds of them — because the information they store comes in different shapes, and each kind does one job better than the others. It's like using the best tool for the job: Anna's profile goes in PostgreSQL, the live chat in Cassandra, and who-knows-whom in Neo4j. That is why “just change the profile page” can touch the UI, the server, and more than one database — and here you can see where those calls land.
There is no single tool that excels at everything. The stack is chosen from product needs, money, growth stage — and a series of tradeoffs between speed, performance, and cost.
Once the software is built, it has to be hosted live so customers can open it. Most of the time, that host is cloud infrastructure.
Cloud infrastructure means the app does not sit on one office computer. It runs on rented machines in data centers (AWS, Google Cloud, Azure, and others) that can grow when traffic spikes and stay up when a single machine fails.
That is how a DuckBuddy profile in Kraków and a chat room in Madrid can load for you at the same time. The HTTPS calls in the picture above are crossing the public internet to those cloud servers — then staying on DuckBuddy's private network when Python talks to PostgreSQL, Redis, Neo4j, MongoDB, and Cassandra.
Mobile apps are the software built specifically for a smartphone (iOS and Android). They often use a completely different front-end stack than the website — Swift, Kotlin, or React Native — but they connect to the exact same back-end and databases.
So a feature on Anna's profile still has to be true in the browser and on the phone, even though those two UIs were not built the same way.
This explorer exists because “just change a few lines of live code” is not how software is updated.
The myth: “Just get a developer to go into the live code and change a few lines.”
Every website and app is built on layers. A new field on a profile may need a React screen, a Python endpoint, a PostgreSQL column, a cache in Redis, a mobile screen that was written separately, tests, and a careful deploy to the cloud — without taking DuckBuddy down for the people already chatting.
Product, engineering, QA, and often marketing all have to weigh in. Then the work is scheduled into a sprint next to everything else the company is already building. That is why even an approved request takes time.
This part of the DuckBuddy Explorer Learning Series is here to help you see those layers, grow your knowledge of how tech stacks work, and understand why software work is rarely as small as it sounds.
Four things worth having at the other side of these pages.
Keep going in order, or jump to any page from the top menu.