What Are Infrastructure & Network Fundamentals?

Key points

  • Infrastructure & Network Fundamentals are the technologies working quietly behind the scenes to support a system — things like communication mechanisms and where servers are hosted — a foundation that's easy to overlook.
  • Representative technologies include TCP/IP, DNS, HTTPS (certificates), and the cloud.
  • Basic infrastructure knowledge is also essential for narrowing down the cause when something goes wrong.
🔌 Communication mechanisms TCP/IP (rules for delivering data) DNS (translates names into addresses)
Security & hosting
🔒☁️ Security & hosting HTTPS (encryption & certificates) Cloud (where servers are hosted)

Teacher Pochi uses the network like this every day, too

🎥 Watching videos 🌐 Browsing sites 🔒 Online banking
TCP/IPWhen I'm streaming a video, how does the data actually make it here from some server far away? DNSHow does just typing a URL reliably land me on the right site? HTTPSThis site has a little lock icon — what exactly is that protecting? Cloud OverviewWhere in the world is this app's data actually stored?

What "infrastructure" actually means

Infrastructure refers to the overall set of mechanisms that form the "foundation" a web app or system needs in order to run. Just as roads, electricity, and water quietly support our everyday lives, networks and servers quietly support systems.

App
(the visible part)
Runs on top of
Infrastructure
(the foundation)

Teacher Pochi's hintInfrastructure is like a house's foundation work. The people living there never see it, but it's precisely because there's a solid foundation that a house (the app) can be built safely on top of it.

Networks and TCP/IP

Our computers and smartphones can exchange data with servers far away because a set of communication rules called "TCP/IP" is used as a common standard worldwide.

Your
computer
Sent via
TCP/IP
Internet
Destination
server

Because the way data is sent and destinations are specified is standardized worldwide, communication works regardless of country or device. We cover the details in the dedicated TCP/IP topic.

Domains and DNS

Servers are actually assigned a numeric address called an "IP address," but since those are hard for people to remember, a text-based address called a "domain" is used instead. DNS is the mechanism that translates a domain into an IP address.

Access
example.com
Query DNS
DNS server
Returns the IP address
Connect to
the server

Teacher Pochi's hintDNS is like a phone book. When you know someone's name but not their phone number, you look it up in the phone book before dialing. We cover the details in the dedicated DNS topic.

HTTPS and secure communication

Communication over the internet is at risk of being intercepted or impersonated along the way. HTTPS encrypts the communication and, using "certificates," also guarantees that the destination is genuine.

🔒 EncryptionKeeps the content of communication unreadable to third parties
📜 CertificateProves the destination is genuine
⚠️ Certificate errorExpired or invalid certificates trigger a warning

Teacher Pochi's hintA certificate is like an ID card. A trusted third party (a certificate authority) vouches that the other side really is who they claim to be (the genuine server). We cover the details in the dedicated HTTPS topic.

Where servers live: on-premises vs. the cloud

The servers that run a system are operated either "on-premises" — where a company buys and installs its own equipment — or in the "cloud," where it rents facilities provided by a cloud provider.

🏢 On-premises Company buys and installs its own servers High upfront cost / high flexibility
☁️ Cloud Rent only as much of a provider's equipment as needed Low upfront cost / scales up or down quickly

Teacher Pochi's hintOn-premises is like owning a home, and the cloud is like renting one. You can freely renovate a home you own, but it comes with a big upfront cost; renting lets you take only the space and duration you need, which keeps things light.

Cloud service models (IaaS, PaaS, SaaS)

Cloud services are mainly divided into three models based on how much the provider prepares for you.

🧱 IaaS Provides servers and networking
🛠️ PaaS Provides the OS and runtime environment
📦 SaaS Provides a fully finished application

The further along this scale you go, the smaller the range the user has to manage, and the more quickly you can get started. We cover the details in the dedicated Cloud Overview topic.

Why infrastructure knowledge matters during incidents

When a "can't access the site" incident happens, the cause could be lurking anywhere — the network, DNS, a certificate, the server, and more. Knowing infrastructure fundamentals lets you narrow it down systematically by working through the likely suspects in order.

Is it DNS?Is the domain returning the right address?
Is it connectivity?Is traffic reaching the server (TCP/IP)?
Is it the certificate?Is the HTTPS certificate valid?

Teacher Pochi's hintJust as a doctor narrows down the cause of an illness by asking "do you have a fever?" and "where does it hurt?" in order, knowing a systematic troubleshooting process matters just as much when responding to infrastructure incidents.

Summary

Infrastructure & Network Fundamentals bring together the technologies that quietly support a system: communication via TCP/IP, name resolution via DNS, secure communication via HTTPS, and server hosting via the cloud.

You can learn more about each of these mechanisms in the dedicated topics below.

Related topics:

🏠 Back to top