Azure / Microsoft 365 / Head in the Clouds: Your Ultimate Guide to Cloud Computing
Azure & Microsoft 365

Head in the Clouds: Your Ultimate Guide to Cloud Computing

Everything you need to know about cloud computing: what it is, the deployment models, service types (IaaS, PaaS, SaaS), benefits, and what’s new in 2026. Your fun, practical starting point for the cloud.

Cloud Computing Azure Microsoft 365 IaaS / PaaS / SaaS Beginner Friendly

Wait… What Even IS “The Cloud”?

Let’s get one thing straight right away: the cloud is not a fluffy thing in the sky storing your vacation photos next to a rainbow. It’s also not magic (though it can feel like it). The cloud is, at its core, a massive network of data centers enormous buildings packed wall to wall with servers, storage systems, and networking gear owned and operated by companies like Microsoft, Amazon, and Google, and made accessible to you and your business over the internet.

Think of it this way: You don’t own the power plant that generates your electricity. You just plug in, use what you need, and pay your bill at the end of the month. Cloud computing works the same way except instead of electricity, you’re consuming servers, databases, software, and storage. Brilliant, right?

The “Before Times”: Life On-Premises

To truly appreciate the cloud, you need to understand what came before it and why it was such a headache.

Imagine you run a company. You need IT infrastructure: servers to run your apps, storage for your files, networking gear to connect everything, and a room (or whole building) to keep it all in, climate controlled, secure, and staffed by IT professionals. All of that hardware? You buy it. You maintain it. You upgrade it. You babysit it at 2am when something breaks.

Now picture this: your company runs an annual conference or a Black Friday style sales event. For two weeks a year, your systems are under enormous stress. So what do you do? You buy MORE servers to handle that peak load. Then for the other 50 weeks of the year, those expensive machines sit in a rack doing absolutely nothing useful, quietly draining your electricity budget.

This is the on-premises model and while it still has legitimate use cases, for most businesses it’s an expensive, inflexible way to manage IT. The cloud was built to fix exactly this problem.

So, What Is Cloud Computing? (The Real Definition)

Cloud computing is the on-demand delivery of computing resources including servers, storage, databases, networking, software, analytics, and intelligence over the internet, on a pay-as-you-go basis.

The key phrase here is on-demand. You don’t need to plan months ahead, order hardware, wait for delivery, and set it all up. You log in to a cloud portal, click a few buttons (or run a script), and within minutes you have a fully functional server, database, or application environment ready to go. And when you’re done? You delete it. You stop paying. That’s it.

The major cloud providers powering this revolution include:

  • Microsoft Azure deeply integrated with enterprise tools and Microsoft 365
  • Amazon Web Services (AWS) the current market share leader with an enormous catalog of services
  • Google Cloud Platform (GCP) strong in AI/ML, data analytics, and Kubernetes
  • IBM Cloud favored in regulated industries like banking and healthcare
  • Oracle Cloud a strong choice for database heavy workloads
  • Salesforce the pioneer of cloud based CRM and business apps

The Three Types of Cloud (Deployment Models)

Not all clouds are created equal. The way you deploy your cloud environment depends on your business’s needs around privacy, cost, compliance, and control.

Here’s a fun analogy: think about how you get to work every day.

  • 🚗 Drive yourself total control, total privacy, but you pay for gas and maintenance yourself.
  • 🚕 Hire a rideshare a nice balance of privacy and convenience, without the ownership costs.
  • 🚌 Take public transit cheapest option, shared with everyone else, but it gets the job done.
🔒 Private Cloud

Like your own car, a private cloud is dedicated exclusively to one organization. It can be hosted on-premises in your own data center, or managed off-premises by a third-party provider, but the key is: nobody else shares it. This is the go-to choice for organizations with strict compliance or regulatory requirements, think banks, hospitals, and government agencies. High control, high cost.

🌐 Public Cloud

This is the bus. Resources are owned and managed by cloud providers and shared across multiple customers (though your data remains isolated and secure). You don’t worry about maintaining anything the cloud provider handles hardware, updates, and security infrastructure. It’s cost efficient, massively scalable, and ideal for most businesses. Services from Azure, AWS, and Google Cloud fall into this category.

🔀 Hybrid Cloud

The rideshare model. A hybrid cloud combines private and public cloud environments, allowing data and applications to move between them. You might keep sensitive customer data in your private cloud while running your public facing website on the public cloud. Best of both worlds and it’s the model most large enterprises are moving toward in 2026.

🏘️ Community Cloud

Less commonly discussed but equally important: a community cloud is a shared infrastructure used by a specific group of organizations with common concerns like multiple hospitals sharing a HIPAA compliant platform, or government agencies sharing a secure collaboration environment. It’s managed internally or by a third party to serve a specific community’s shared needs.

The Three Service Models: What Does the Cloud Give You?

Great, so you’re using the cloud. But what exactly are you getting? Cloud services are typically broken into three layers, often visualized as a stack:

🏗️ Infrastructure as a Service (IaaS)

This is the raw building blocks of IT delivered over the internet. We’re talking virtual machines, storage, networking, and firewalls all provisioned on demand. You get the infrastructure; you’re responsible for everything on top of it (operating system, middleware, applications, security configuration).

Think of IaaS like renting an empty apartment. You have the walls, plumbing, and electricity but you have to bring your own furniture and decorate it yourself.
  • Examples: Azure Virtual Machines, AWS EC2, Google Compute Engine
  • Best for: IT teams who need full control over their environments and companies migrating existing workloads
🛠️ Platform as a Service (PaaS)

Here, the cloud provider manages the infrastructure AND the underlying platform the operating system, runtime environment, patching, and scaling. You just focus on writing and deploying your code.

PaaS is a furnished apartment. The furniture is already there, the utilities are managed, you just move in and live your life.
  • Examples: Azure App Service, Google App Engine, AWS Elastic Beanstalk, Heroku
  • Best for: Developers and teams who want to build applications fast without worrying about the infrastructure underneath
💻 Software as a Service (SaaS)

This is cloud computing at its most accessible. With SaaS, the provider manages absolutely everything infrastructure, platform, AND the application. You simply open a browser and use the software. No installation, no updates, no maintenance.

SaaS is the hotel room. Everything is set up for you. You just show up.
  • Examples: Microsoft 365, Google Workspace, Salesforce, Slack, Zoom, Dropbox
  • Best for: End users and businesses who want ready to use software with minimal IT overhead

The Benefits of Cloud Computing

💰 Cost Efficiency

The cloud shifts IT spending from CapEx (capital expenditure) to OpEx (operational expenditure). Instead of buying $500,000 worth of servers that depreciate the moment they arrive, you pay for only what you consume, when you consume it. For startups and scaling businesses, this is a game changer.

🚀 Scalability and Elasticity

Need 100 servers for an event this weekend and 5 servers next week? No problem. The cloud lets you scale up and scale down instantly, matching your resource usage to your actual demand. This is called elasticity, and it’s one of the most powerful features of modern cloud platforms.

🌍 Global Reach

Cloud providers operate data centers in dozens of regions around the world. This means you can deploy your applications closer to your users, reducing latency and improving performance without ever physically leaving your office.

🔐 Security (That Actually Scales)

Cloud providers invest billions of dollars annually in security infrastructure, dedicated security teams, AI powered threat detection, compliance certifications (SOC 2, ISO 27001, HIPAA, FedRAMP), and physical data center security that most organizations could never afford to replicate on their own. Your data is encrypted in transit and at rest, and access is tightly controlled.

Security in the cloud is a shared responsibility. The cloud provider secures the infrastructure; you’re responsible for securing what you put on it (access controls, patching your apps, managing identities).
⚡ Speed and Agility

In the old world, spinning up a new server could take weeks, procurement, delivery, setup. In the cloud, it takes minutes. This dramatically accelerates development cycles, testing, and time to market for new products and services.

🔄 Reliability and Disaster Recovery

Top cloud providers offer 99.9%+ uptime SLAs (Service Level Agreements), with built in redundancy across multiple data centers. If one facility has an issue, your workloads automatically fail over to another. Setting up this kind of resilience on premises would be enormously expensive.

🌱 Sustainability

Major cloud providers are investing heavily in renewable energy and carbon neutral operations. Microsoft has committed to being carbon negative by 2030. By moving to the cloud, organizations can reduce their own environmental footprint significantly compared to running inefficient on premises data centers.

Cloud Computing in 2026: What’s New?

🤖 AI and Machine Learning as a Service

Every major cloud provider now offers powerful, easy to consume AI services. From Azure OpenAI Service (the tech behind ChatGPT) to Google’s Vertex AI and AWS SageMaker, you can integrate cutting edge AI into your apps without a PhD in machine learning.

🔣 Serverless Computing

Functions as a Service (FaaS) platforms like Azure Functions, AWS Lambda, and Google Cloud Functions let developers run code without managing servers at all. You write the function, the cloud figures out everything else. You only pay when the code actually runs.

🏭 Edge Computing

Not everything can (or should) live in a centralized data center. Edge computing brings processing power closer to where data is generated think IoT devices, manufacturing floors, and retail stores. Expect more hybrid edge to cloud architectures in the coming years.

🔐 Zero Trust Security

The old “castle and moat” model of network security is dead. Zero Trust, the principle of “never trust, always verify,” is now the dominant security philosophy in cloud environments, especially with distributed workforces.

🌐 Multi-Cloud Strategies

Most large enterprises now use services from two or more cloud providers simultaneously, avoiding vendor lock in and optimizing for specific workloads.

Quick Reference: Cloud Cheat Sheet

IaaSPaaSSaaS
You manageOS, apps, dataApps, dataJust data/usage
Provider managesHardware, networkingHardware, OS, runtimeEverything
AnalogyEmpty apartmentFurnished apartmentHotel room
ExampleAzure VMsAzure App ServiceMicrosoft 365
Best forFull controlFast devEnd users

Final Thoughts: Should You Be on the Cloud?

Short answer: you probably already are, whether you know it or not. Every time you use Gmail, watch Netflix, collaborate in Teams, or check your bank balance on your phone, you’re consuming cloud services.

For businesses, the question in 2026 is no longer “should we move to the cloud?” It’s “how do we move to the cloud strategically?” optimizing for cost, security, performance, and compliance.

The cloud democratizes access to world class technology. A two person startup today has access to the same AI, global infrastructure, and security tools as a Fortune 500 company. That’s genuinely remarkable, and it’s only getting more powerful.

So whether you’re just starting your cloud journey or looking to deepen your expertise, the sky isn’t the limit. The cloud is.

Want to go deeper? Explore certifications like Microsoft Azure Fundamentals (AZ-900), AWS Cloud Practitioner, or Google Associate Cloud Engineer to kickstart your cloud career.

Azure / Computer Networks: Types and Topology Explained
Azure

Computer Networks: Types and Topology Explained

From Bluetooth earbuds to global cloud infrastructure every connection is a network. This guide covers what a network is, the seven major types, and all key topologies with real-world examples and pros and cons for each.

Networking LAN / WAN Topology Cloud Fundamentals Beginner Friendly

What Is a Network?

A network is a collection of connected devices called nodes that share data and resources with each other. These nodes can be computers, phones, printers, servers, routers, or any hardware.

Devices connect via cables, Wi-Fi, Bluetooth, fiber optics, or cellular links. The purpose is communication, collaboration, resource sharing, and remote access.

Think of it like a transport system. Devices are destinations, data is the traffic, and switches or routers are the junctions that direct traffic to the right place.

Network Types

Networks are classified by geographic reach how far they extend and how many locations they connect. From smallest to largest: PAN → LAN → CAN → MAN → WAN.

1. Personal Area Network (PAN)

A PAN connects devices belonging to a single person, typically over 110 meters using Bluetooth or USB.

  • Examples: Phone + smartwatch, laptop + wireless mouse, phone + Bluetooth earbuds
  • Pros: Easy to set up, convenient, low power consumption
  • Cons: Very short range, limited device count, not suited for shared organizational networks
2. Local Area Network (LAN)

A LAN connects devices within a limited area a room, home, office, or school building using Ethernet and Wi-Fi.

  • Examples: Home Wi-Fi, office network, school computer lab, library network
  • Pros: Fast local communication, easy file/printer/internet sharing, lower cost
  • Cons: Limited to one local site, needs administration and security
3. Campus Area Network (CAN)

A CAN connects multiple LANs across a single campus or organization university, hospital complex, or business park up to a few kilometers.

  • Examples: University campus, airport terminals, hospital blocks, corporate parks
  • Pros: Centralized control, fast inter-department sharing, good security
  • Cons: Higher setup cost, needs backbone planning, complex troubleshooting
4. Metropolitan Area Network (MAN)

A MAN links multiple LANs or CANs across an entire city or metro area, typically over high-capacity metro fiber.

  • Examples: Government offices across a city, banks with many branches, city education systems
  • Pros: Connects many urban locations efficiently, supports high bandwidth
  • Cons: More expensive, depends on service provider infrastructure
5. Wide Area Network (WAN)

A WAN connects networks over long distances across regions, countries, or continents. The internet is the largest WAN in existence.

  • Examples: Multinational company networks, banking networks, cloud connectivity, the internet
  • Pros: Global reach, supports cloud access, scales for large organizations
  • Cons: Higher latency, costly, harder to secure
6. Virtual Private Network (VPN)

A VPN creates a secure, encrypted tunnel over a public network, acting as a private intermediary between your device and the destination.

  • Examples: Remote workers accessing company resources, secure browsing on public Wi-Fi
  • Pros: Strong security and privacy, useful for remote access, masks IP
  • Cons: Can reduce speed, depends on provider quality
7. Wireless LAN (WLAN)

A WLAN is a LAN that uses wireless connections (Wi-Fi) instead of cables, giving users mobility within the coverage area.

  • Examples: Coffee shop Wi-Fi, home router, office wireless network
  • Pros: Cable-free, easy to add devices, mobile freedom
  • Cons: Susceptible to interference and security risks, slower than wired
TypeRangeSimple ExampleMain StrengthMain Drawback
PAN~110 mPhone + earbudsPersonal & convenientVery short range
LANRoom to buildingHome Wi-FiFast local sharingLimited coverage
CANUp to a few kmUniversity campusCentral controlHigher cost
MANCity-wideCity bank branchesUrban connectivityProvider-dependent
WANRegional to globalThe internetWorldwide reachHigher latency
VPNAny distanceRemote work accessEncrypted securitySpeed overhead
WLANRoom to buildingOffice Wi-FiCable-free mobilityInterference risk

Network Topology

Network topology is the arrangement of devices and connections within a network how computers, switches, routers, and links are organized, and how data flows between them.

  • Physical topology: The actual layout of cables and hardware
  • Logical topology: How data flows, which may differ from the physical layout
  • Why it matters: Topology affects cost, speed, reliability, troubleshooting, and scalability
1. Star Topology

Every device connects to a central hub or switch. The most common design in modern home and office Ethernet networks.

  • Example: Office PCs and printers all connected to one switch
  • Pros: Easy to add/remove devices, simple to troubleshoot, one cable failure only affects one device
  • Cons: Central switch is a single point of failure, uses more cabling, can be overloaded
2. Bus Topology

All devices share a single backbone cable. Historically important, less common today.

  • Example: Early Ethernet networks using one shared coaxial cable
  • Pros: Simple layout, low cable cost, easy to understand
  • Cons: Backbone failure stops the whole network, performance drops with more devices
3. Ring Topology

Each device connects to two neighbors forming a closed loop. Data travels around the ring to reach its destination.

  • Example: Industrial control networks, metro ring designs
  • Pros: Orderly and predictable data flow, avoids collisions, useful with dual-ring redundancy
  • Cons: One break can disrupt the ring, adding devices may interrupt the network
4. Mesh Topology

Devices have multiple interconnections. A full mesh connects every node to every other; a partial mesh connects only critical paths.

  • Example: Internet backbones, data centers, wireless mesh Wi-Fi systems
  • Pros: Very reliable, excellent fault tolerance, traffic flows even during failures
  • Cons: Expensive to build, complex to design and manage
5. Tree Topology

A hierarchical design combining multiple star networks under higher-level switches a mix of star and bus topology.

  • Example: Enterprise campus networks, school networks with core and floor switches
  • Pros: Scales well, easy to organize by layers or departments, good segmentation
  • Cons: Upper-level failures cascade, requires more planning and equipment
6. Hybrid Topology

A combination of two or more topology types. Most real-world organizational networks are hybrid because they grow and evolve over time.

  • Example: Star topology inside each floor + tree or mesh backbone between floors
  • Pros: Very flexible, mixes strengths of multiple topologies
  • Cons: More complex to design, higher cost, troubleshooting spans multiple types
7. Point-to-Point Topology

A direct, dedicated link between exactly two devices the simplest topology of all.

  • Example: A direct leased line between two office locations, a serial link between two routers
  • Pros: Simple, guaranteed bandwidth, easy to secure
  • Cons: Only connects two devices, not scalable for multiple nodes
TopologyWhat it looks likeSimple ExampleMain StrengthMain Weakness
StarDevices around one central switchSmall office LANEasy managementCentral switch is a single point of failure
BusDevices on one backbone cableOlder Ethernet labLow cabling costBackbone failure affects all
RingDevices form a closed loopIndustrial networkPredictable flowBreak disrupts traffic
MeshMultiple links between devicesData center backboneHigh reliabilityHigh cost and complexity
TreeHierarchical layers of starsEnterprise campusOrganized & scalableUpper-level failures cascade
HybridMix of topologiesMulti-floor officeFlexibleComplex to manage
Point-to-PointDirect link between 2 devicesLeased WAN linkSimple & reliableNot scalable

Key Takeaways

  • A network is any group of connected devices that communicate and share resources.
  • Network types (PAN through WAN) differ primarily by geographic range and the number of locations they connect.
  • Network topology describes how devices are arranged and how data flows it affects cost, reliability, and scalability.
  • Most real-world networks are hybrid, combining elements of multiple topologies to fit organizational needs.
Exam tip: Pair each network type and topology with one concrete example to remember it faster. PAN = earbuds, Star = office switch, Mesh = internet backbone.
Azure / Computer Networks: Types and Topology Explained
Azure

Computer Networks: Types and Topology Explained

From Bluetooth earbuds to global cloud infrastructure every connection is a network. This guide covers what a network is, the seven major types, and all key topologies with real-world examples and pros and cons for each.

Networking LAN / WAN Topology Cloud Fundamentals Beginner Friendly

What Is a Network?

A network is a collection of connected devices called nodes that share data and resources with each other. These nodes can be computers, phones, printers, servers, routers, or any hardware.

Devices connect via cables, Wi-Fi, Bluetooth, fiber optics, or cellular links. The purpose is communication, collaboration, resource sharing, and remote access.

Think of it like a transport system. Devices are destinations, data is the traffic, and switches or routers are the junctions that direct traffic to the right place.

Network Types

Networks are classified by geographic reach how far they extend and how many locations they connect. From smallest to largest: PAN → LAN → CAN → MAN → WAN.

1. Personal Area Network (PAN)

A PAN connects devices belonging to a single person, typically over 110 meters using Bluetooth or USB.

  • Examples: Phone + smartwatch, laptop + wireless mouse, phone + Bluetooth earbuds
  • Pros: Easy to set up, convenient, low power consumption
  • Cons: Very short range, limited device count, not suited for shared organizational networks
2. Local Area Network (LAN)

A LAN connects devices within a limited area a room, home, office, or school building using Ethernet and Wi-Fi.

  • Examples: Home Wi-Fi, office network, school computer lab, library network
  • Pros: Fast local communication, easy file/printer/internet sharing, lower cost
  • Cons: Limited to one local site, needs administration and security
3. Campus Area Network (CAN)

A CAN connects multiple LANs across a single campus or organization university, hospital complex, or business park up to a few kilometers.

  • Examples: University campus, airport terminals, hospital blocks, corporate parks
  • Pros: Centralized control, fast inter-department sharing, good security
  • Cons: Higher setup cost, needs backbone planning, complex troubleshooting
4. Metropolitan Area Network (MAN)

A MAN links multiple LANs or CANs across an entire city or metro area, typically over high-capacity metro fiber.

  • Examples: Government offices across a city, banks with many branches, city education systems
  • Pros: Connects many urban locations efficiently, supports high bandwidth
  • Cons: More expensive, depends on service provider infrastructure
5. Wide Area Network (WAN)

A WAN connects networks over long distances across regions, countries, or continents. The internet is the largest WAN in existence.

  • Examples: Multinational company networks, banking networks, cloud connectivity, the internet
  • Pros: Global reach, supports cloud access, scales for large organizations
  • Cons: Higher latency, costly, harder to secure
6. Virtual Private Network (VPN)

A VPN creates a secure, encrypted tunnel over a public network, acting as a private intermediary between your device and the destination.

  • Examples: Remote workers accessing company resources, secure browsing on public Wi-Fi
  • Pros: Strong security and privacy, useful for remote access, masks IP
  • Cons: Can reduce speed, depends on provider quality
7. Wireless LAN (WLAN)

A WLAN is a LAN that uses wireless connections (Wi-Fi) instead of cables, giving users mobility within the coverage area.

  • Examples: Coffee shop Wi-Fi, home router, office wireless network
  • Pros: Cable-free, easy to add devices, mobile freedom
  • Cons: Susceptible to interference and security risks, slower than wired
TypeRangeSimple ExampleMain StrengthMain Drawback
PAN~110 mPhone + earbudsPersonal & convenientVery short range
LANRoom to buildingHome Wi-FiFast local sharingLimited coverage
CANUp to a few kmUniversity campusCentral controlHigher cost
MANCity-wideCity bank branchesUrban connectivityProvider-dependent
WANRegional to globalThe internetWorldwide reachHigher latency
VPNAny distanceRemote work accessEncrypted securitySpeed overhead
WLANRoom to buildingOffice Wi-FiCable-free mobilityInterference risk

Network Topology

Network topology is the arrangement of devices and connections within a network how computers, switches, routers, and links are organized, and how data flows between them.

  • Physical topology: The actual layout of cables and hardware
  • Logical topology: How data flows, which may differ from the physical layout
  • Why it matters: Topology affects cost, speed, reliability, troubleshooting, and scalability
1. Star Topology

Every device connects to a central hub or switch. The most common design in modern home and office Ethernet networks.

  • Example: Office PCs and printers all connected to one switch
  • Pros: Easy to add/remove devices, simple to troubleshoot, one cable failure only affects one device
  • Cons: Central switch is a single point of failure, uses more cabling, can be overloaded
2. Bus Topology

All devices share a single backbone cable. Historically important, less common today.

  • Example: Early Ethernet networks using one shared coaxial cable
  • Pros: Simple layout, low cable cost, easy to understand
  • Cons: Backbone failure stops the whole network, performance drops with more devices
3. Ring Topology

Each device connects to two neighbors forming a closed loop. Data travels around the ring to reach its destination.

  • Example: Industrial control networks, metro ring designs
  • Pros: Orderly and predictable data flow, avoids collisions, useful with dual-ring redundancy
  • Cons: One break can disrupt the ring, adding devices may interrupt the network
4. Mesh Topology

Devices have multiple interconnections. A full mesh connects every node to every other; a partial mesh connects only critical paths.

  • Example: Internet backbones, data centers, wireless mesh Wi-Fi systems
  • Pros: Very reliable, excellent fault tolerance, traffic flows even during failures
  • Cons: Expensive to build, complex to design and manage
5. Tree Topology

A hierarchical design combining multiple star networks under higher-level switches a mix of star and bus topology.

  • Example: Enterprise campus networks, school networks with core and floor switches
  • Pros: Scales well, easy to organize by layers or departments, good segmentation
  • Cons: Upper-level failures cascade, requires more planning and equipment
6. Hybrid Topology

A combination of two or more topology types. Most real-world organizational networks are hybrid because they grow and evolve over time.

  • Example: Star topology inside each floor + tree or mesh backbone between floors
  • Pros: Very flexible, mixes strengths of multiple topologies
  • Cons: More complex to design, higher cost, troubleshooting spans multiple types
7. Point-to-Point Topology

A direct, dedicated link between exactly two devices the simplest topology of all.

  • Example: A direct leased line between two office locations, a serial link between two routers
  • Pros: Simple, guaranteed bandwidth, easy to secure
  • Cons: Only connects two devices, not scalable for multiple nodes
TopologyWhat it looks likeSimple ExampleMain StrengthMain Weakness
StarDevices around one central switchSmall office LANEasy managementCentral switch is a single point of failure
BusDevices on one backbone cableOlder Ethernet labLow cabling costBackbone failure affects all
RingDevices form a closed loopIndustrial networkPredictable flowBreak disrupts traffic
MeshMultiple links between devicesData center backboneHigh reliabilityHigh cost and complexity
TreeHierarchical layers of starsEnterprise campusOrganized & scalableUpper-level failures cascade
HybridMix of topologiesMulti-floor officeFlexibleComplex to manage
Point-to-PointDirect link between 2 devicesLeased WAN linkSimple & reliableNot scalable

Key Takeaways

  • A network is any group of connected devices that communicate and share resources.
  • Network types (PAN through WAN) differ primarily by geographic range and the number of locations they connect.
  • Network topology describes how devices are arranged and how data flows it affects cost, reliability, and scalability.
  • Most real-world networks are hybrid, combining elements of multiple topologies to fit organizational needs.
Exam tip: Pair each network type and topology with one concrete example to remember it faster. PAN = earbuds, Star = office switch, Mesh = internet backbone.
Linux / Linux Basic / Understanding Linux commands
Linux Basic

Understanding Linux commands

The ls command short for list is the first command most people learn on Linux. It shows you what’s inside a directory. This guide takes you from the basics all the way to exploring the root filesystem and /etc/ with real simulated terminal output.

Command Line File System ls Linux Basics

What is ls?

ls stands for list. It prints the names of files and directories inside a folder. Run it with no arguments and it lists your current working directory. Pass a path and it lists that path instead.

Basic syntax
ls                  # list current directory
ls /path/to/dir     # list a specific path
ls ~                # list your home directory (~ = home)
Try it now: Open a terminal and type ls followed by Enter. You’ll see the contents of wherever you are right now.

Key Flags & Options

Flags change how ls behaves. You can combine them freely. Here are the most important ones:

FlagLong formWhat it does
-a–allShow hidden files (names starting with .)
-lLong format permissions, owner, size, date
-h–human-readableHuman-readable sizes (4.0K, 12M) requires -l
-1One entry per line (the number 1, not letter L)
-tSort by modification time, newest first
-r–reverseReverse the sort order
-R–recursiveList all subdirectories recursively
-SSort by file size, largest first
-F–classifyAppend type indicators (/ for dirs, * for executables)
-i–inodeShow inode numbers
-d–directoryList directories themselves, not their contents

Popular Combinations

Most-used ls combos
ls -la     # long format + show hidden files
ls -lh     # long format + human-readable sizes
ls -ltr    # long format + sorted by time, oldest first
ls -lAh    # long format + all (except . and ..) + human sizes
ls -1      # one item per line, clean for piping

Pro Tips

Many Linux systems define shell aliases so you don’t have to type the full flags every time:

Common ls aliases (often in ~/.bashrc)
alias ll='ls -lh'        # long + human-readable
alias la='ls -lAh'       # long + all hidden + human-readable
alias l='ls -1'          # one per line
Read the manual: Run man ls for the complete reference. Press q to exit. You can also combine ls with pipes: ls /etc | grep ssh

Exploring the Root Filesystem with ls /

The root directory / is the top of the entire Linux filesystem. Everything lives inside it. Running ls / gives you the Filesystem Hierarchy Standard (FHS) the standardised layout used by all major Linux distributions.

List the root filesystem
$ ls /
bin   boot  dev  etc  home  lib  lib64  media  mnt  opt
proc  root  run  sbin  srv  sys  tmp  usr  var

Here is what each top-level directory does:

DirectoryPurpose
/binEssential user binaries (ls, cp, mv, bash, etc.)
/sbinSystem administration binaries (only root typically uses these)
/etcSystem-wide configuration files the most important directory
/homePersonal directories for each user (/home/username)
/varVariable data logs (/var/log), databases, mail spools
/devDevice files (hard drives, USB, terminals everything is a file)
/procVirtual filesystem live kernel and process information
/sysVirtual filesystem hardware and kernel subsystem info
/tmpTemporary files, cleared on reboot
/bootBootloader and kernel images
/usrUser programs, libraries, and documentation
/rootHome directory for the root user (not /home/root)
/runRuntime data since last boot (PIDs, sockets)
/libShared libraries needed by /bin and /sbin
/mntMount point for temporarily mounted filesystems
/optOptional/add-on software packages

Navigate to root and explore

Change into root and confirm location
$ cd /
$ pwd
/

Now run ls -lh from here to see the root directory in long format with human-readable sizes:

ls -lh from /
$ ls -lh
total 72K
lrwxrwxrwx   1 root root    7 Apr  1  2024 bin -> usr/bin
drwxr-xr-x   4 root root 4.0K Jan 15 08:22 boot
drwxr-xr-x  19 root root 3.8K Apr  3 10:01 dev
drwxr-xr-x 133 root root  12K Apr  3 09:55 etc
drwxr-xr-x   3 root root 4.0K Mar 29 18:42 home
lrwxrwxrwx   1 root root    7 Apr  1  2024 lib -> usr/lib
drwx------   2 root root  16K Mar 28 11:00 lost+found
drwxr-xr-x   2 root root 4.0K Mar 28 11:00 media
drwxr-xr-x   2 root root 4.0K Mar 28 11:00 mnt
drwxr-xr-x   5 root root 4.0K Apr  1 10:35 opt
dr-xr-xr-x 220 root root    0 Apr  3 10:01 proc
drwx------   5 root root 4.0K Apr  3 11:30 root
drwxr-xr-x  30 root root  840 Apr  3 10:01 run
lrwxrwxrwx   1 root root    8 Apr  1  2024 sbin -> usr/sbin
drwxr-xr-x   2 root root 4.0K Apr  1  2024 srv
dr-xr-xr-x  13 root root    0 Apr  3 10:01 sys
drwxrwxrwt  12 root root 4.0K Apr  3 11:28 tmp
drwxr-xr-x  14 root root 4.0K Apr  1  2024 usr
drwxr-xr-x  12 root root 4.0K Apr  1 10:35 var
Navigation shortcuts: cd ~ takes you back to your home directory. cd - takes you back to the previous directory. pwd always shows you where you are.

Testing ls Flag Variations in /

Now that you are in /, let’s experiment with different flag combinations. This is where most beginners learn what each flag actually does by seeing real output.

ls -1 one entry per line

ls -1 (number one, not letter L)
$ ls -1
bin
boot
dev
etc
home
lib
lib64
media
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var

The -1 flag (the digit 1) forces one item per line clean and easy to pipe into grep, wc, or other tools.

ls -1 -h does -h work without -l?

ls -1 -h in /
$ ls -1 -h
bin
boot
dev
etc
home
lib
lib64
media
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var
Important: The -h flag (human-readable sizes) has no effect without -l. Sizes only appear in long format. To see sizes, use ls -1lh instead.

ls -a and ls –all hidden files

ls -a in /
$ ls -a
.   ..   bin   boot   dev   etc   home   lib   lib64
media   mnt   opt   proc   root   run   sbin   srv
sys   tmp   usr   var

The -a flag reveals hidden items those whose names begin with a dot. Every directory has . (current directory) and .. (parent directory) as special hidden entries. The real / on most systems has almost no other hidden files, but home directories have many (like .bashrc, .ssh/, .gitconfig).

–all is the same as -a
$ ls --all
.   ..   bin   boot   dev   etc   home   lib   lib64
media   mnt   opt   proc   root   run   sbin   srv
sys   tmp   usr   var
Long vs short flags: -a and --all are identical. Short flags are faster to type; long flags are more readable in scripts.

Diving into /etc/ System Configuration

/etc/ is the most important configuration directory on a Linux system. Every major service networking, SSH, DNS, package management, user accounts stores its configuration files here.

ls -1 /etc/ full listing

List /etc/ one entry per line
$ ls -1 /etc/
adduser.conf
alternatives/
apt/
bash.bashrc
ca-certificates.conf
cron.d/
cron.daily/
cron.hourly/
cron.monthly/
cron.weekly/
crontab
default/
environment
fstab
grub.d/
group
gshadow
hostname
hosts
init.d/
inputrc
issue
locale.gen
logrotate.conf
logrotate.d/
lsb-release
machine-id
motd
network/
nsswitch.conf
os-release
pam.d/
passwd
profile
profile.d/
protocols
resolv.conf
security/
services
shadow
shells
ssh/
ssl/
sudoers
sudoers.d/
sysctl.conf
sysctl.d/
systemd/
timezone
udev/
vim/
X11/

Here are the most important files and directories in /etc/:

PathPurpose
/etc/passwdUser account database (username, UID, home, shell)
/etc/shadowEncrypted user passwords (root-readable only)
/etc/groupGroup definitions
/etc/sudoersWho can run sudo and with what permissions
/etc/fstabFilesystem mount table auto-mounts at boot
/etc/hostnameThe machine’s hostname
/etc/hostsStatic hostname-to-IP mappings
/etc/resolv.confDNS resolver settings
/etc/ssh/SSH server and client configuration
/etc/systemd/Systemd service definitions and overrides
/etc/apt/APT package manager configuration (Debian/Ubuntu)
/etc/cron.d/System cron jobs
/etc/profileSystem-wide shell environment settings
/etc/os-releaseOS identity (name, version, ID)

Why ls -1 /etc/ -h has no effect

Remember: -h only affects the size column in -l (long format). Without -l, there is no size column to format, so -h silently does nothing. Use ls -lh /etc/ to see sizes.

Useful /etc/ exploration commands

Practical /etc/ commands
ls -la /etc/          # full details including hidden files
ls /etc/ | grep ssh   # find SSH-related configs
ls -lh /etc/ssh/      # detailed view of SSH config dir
cat /etc/os-release   # show current OS version
cat /etc/hostname     # show the machine hostname
Next steps: Try ls -lh /etc/ssh/ to see SSH configs, ls /etc/apt/ for package manager settings, or ls -la ~ to see all the hidden dot-files in your home directory.
Linux / Linux Basic / Linux & Proxmox Fundamentals
Linux Basic

Linux & Proxmox Fundamentals: Shell Prompts, Commands, and /etc

Before you touch a single VM or config file, you need to understand what the shell is telling you, how every Linux command is built, and where the system keeps its configuration. This guide covers it all.

Proxmox VE Shell Prompt $ # ~ Commands /etc Directory Linux Basics

What is Proxmox VE?

Proxmox Virtual Environment (PVE) is a free, open-source, enterprise-grade server virtualization platform built on Debian Linux. It combines two powerful virtualization technologies into one browser-managed solution:

  • KVM/QEMU Full virtual machines (Windows, Linux, BSD, etc.)
  • LXC Lightweight Linux containers

You manage everything from a clean web interface at https://YOUR-IP:8006. The current version (9.x) runs on Debian 13 (Trixie) with Linux kernel 6.17+, is free under AGPLv3, and is a popular cost-effective alternative to VMware vSphere.

Hardware requirements: 64-bit CPU with Intel VT-x or AMD-V, at least 8 GB RAM, and a 32 GB+ SSD/NVMe for the host OS.

Shell Prompt Symbols: $, #, and ~

When you open a terminal or SSH into a Proxmox server, the shell prompt gives you two critical pieces of information at a glance: who you are and where you are in the filesystem.

$ Regular (Non-Root) User
Regular user prompt
user@pve:~$

The dollar sign means you are logged in as a regular user with limited privileges. Most Proxmox management commands will fail or require sudo from this prompt.

Behaviour at the $ prompt
user@pve:~$ ls /etc           # Works fine
user@pve:~$ apt update        # Permission denied
user@pve:~$ sudo apt update   # Works with sudo
# Root User (Administrator)
Root user prompt
root@pve:~#

The hash sign means you are root full, unrestricted system access. No sudo needed. This is the default on a fresh Proxmox install and what every official guide assumes.

Common root commands in Proxmox
root@pve:~# apt update && apt full-upgrade -y
root@pve:~# qm start 100
root@pve:~# zpool status
Pro Tip: If a command fails unexpectedly, check your prompt first. Running admin commands as $ instead of # is the most common beginner mistake in Proxmox.
~ Home Directory Shortcut

The tilde in your prompt shows you are in your home directory. It is also a shortcut in any command. As root, ~ = /root. As a regular user, ~ = /home/username.

Using ~ in commands
cd ~             # Jump to home from anywhere
cd ~/backups     # Navigate to a subfolder of home
ls ~             # List home directory contents
nano ~/.bashrc   # Edit your Bash configuration
SymbolMeaningPrivilegeHome Path
$Regular user promptLimited needs sudo/home/username
#Root user promptFull administrator/root
~Home directory shortcutDepends on current user

Command Structure: Command, Option, Argument

Every Linux command follows the same universal three-part pattern. Learn this once and any new tool becomes easier to understand.

Universal Linux syntax
command [options] [arguments]

The command is the program to run. Options modify its behaviour short with one dash (-y), long with two (--yes). Arguments are the specific targets it acts on a VM ID, file path, hostname, etc.

Annotated examples
# command: ls | option: -1 | argument: /etc
root@pve:~# ls -1 /etc

# command: qm | sub-command: start | argument: 101
root@pve:~# qm start 101

# command: apt | sub-command: upgrade | option: -y
root@pve:~# apt upgrade -y
Create a VM command + argument + multiple options
root@pve:~# qm create 101 \
  --name "UbuntuServer" \
  --memory 4096 \
  --cores 2 \
  --net0 virtio,bridge=vmbr0 \
  --scsi0 local-lvm:32
Other common Proxmox commands
qm shutdown 101 --timeout 60          # Shutdown VM with timeout
pct create 201 local:vztmpl/debian-12-standard_12.0-1_amd64.tar.zst \
  --hostname debian-ct --memory 1024   # Create container
pvesm list local-zfs                  # List storage contents
pvecm status                          # Check cluster status
Best practices: Use long options (--memory not -m) in scripts they are self-documenting. Quote values with spaces: --name "My VM". Press Tab for auto-completion. Run man qm or qm --help when stuck.

Navigating /etc The Configuration Directory

/etc is the central home for system-wide configuration files in any Linux system. Every major service networking, SSH, DNS, package management, user accounts stores its settings here. In Proxmox, it also holds all VM, container, and cluster definitions.

Navigate into /etc
root@pve:~# cd /etc
root@pve:/etc#

Notice the prompt updates from ~ to /etc once inside. Useful navigation commands:

Directory navigation
cd /etc     # Go to /etc from anywhere
pwd         # Confirm your location
cd -        # Go back to the previous directory
cd ~        # Return to home (/root as root)
List /etc one entry per line
root@pve:~# ls -1 /etc

The -1 flag (the number one, not the letter L) prints one entry per line clean and easy to pipe into grep.

Useful /etc listing variations
ls -1 /etc              # One per line
ls -la /etc             # Detailed: permissions, sizes, dates
ls /etc | grep ssh      # Find SSH-related configs
ls -1 /etc/pve/         # Explore the Proxmox config folder
PathPurpose
/etc/hostnameThe server’s hostname
/etc/hostsStatic hostname-to-IP mappings
/etc/resolv.confDNS resolver settings
/etc/fstabFilesystem mount table
/etc/ssh/sshd_configSSH server configuration
/etc/network/interfacesNetwork config bridges, bonds, VLANs
/etc/apt/sources.list.d/APT repository definitions
/etc/pve/Proxmox cluster filesystem all VM/CT configs, storage, user data
/etc/pve/storage.cfgStorage pool definitions
/etc/pve/datacenter.cfgGlobal Proxmox settings
Practical /etc commands for Proxmox
cat /etc/pve/storage.cfg        # View storage definitions
cat /etc/network/interfaces     # View network config
cat /etc/os-release             # View OS and kernel version
ls /etc/apt/sources.list.d/     # Check APT repositories
Important: Files in /etc are readable by all users, but only root can edit them. Always back up before modifying a config in production a typo in /etc/network/interfaces can cut off SSH access entirely.

cp /etc/network/interfaces /etc/network/interfaces.bak
Summary: The # prompt means root access. The ~ shortcut means home directory. Every command follows command [options] [arguments]. And /etc is where Linux keeps all its configuration. Master these four things and no Proxmox guide or man page will feel foreign.
Linux / Linux Basic / Linux: The OS That Runs the World
Linux Basic

Linux: The OS That Runs the World

From a Finnish student’s hobby project in 1991 to the invisible backbone of the modern internet. Here is the history of Linux, how it works, where it runs, and why every engineer should understand it.

Linux Kernel Open Source GNU/Linux Distributions History Engineers

A Brief History

The story of Linux begins in 1991 with a Finnish computer science student named Linus Torvalds. Frustrated with the limitations of MINIX a Unix-like teaching OS that could not be freely modified he announced on a Usenet mailing list that he was building a “free operating system (just a hobby, won’t be big and professional like GNU).” That hobby became one of the most consequential pieces of software ever written.

Torvalds released the first Linux kernel (version 0.01) in September 1991. Just 10,000 lines of code but it was free, open, and built on solid Unix principles. Combined with the GNU Project’s user-space tools that Richard Stallman’s team had been assembling since 1983, the two together formed the world’s first fully free, Unix-like operating system: GNU/Linux.

Through the 1990s, Linux grew explosively. The internet era created enormous demand for stable, free server software. Companies like Red Hat commercialized it, universities taught it, and a global developer community contributed patches. By the early 2000s, Linux was the backbone of the web. By 2026, the stable kernel sits at version 6.19+, maintained by thousands of contributors worldwide.

What Makes Linux Different

At its core, Linux is a monolithic kernel a single privileged program that manages the CPU, memory, file systems, device drivers, and networking for everything running above it. Unlike proprietary systems, every line of that kernel is publicly readable, auditable, and modifiable under the GNU GPL license.

This openness gave rise to distributions complete operating systems built on top of the Linux kernel, packaged with GNU tools, a desktop environment, a package manager, and thousands of applications. Ubuntu, Fedora, Debian, Arch, and hundreds of others each make different trade-offs between stability, cutting-edge features, simplicity, and customization.

Where Linux Lives Today

Linux’s dominance is quiet but absolute:

  • Servers & Cloud Over 90% of public cloud workloads run on Linux. AWS, Google Cloud, and Azure are all built on it.
  • Mobile Android, the world’s most used mobile OS, runs on the Linux kernel.
  • Supercomputers 100% of the TOP500 supercomputers run Linux.
  • Embedded Systems Routers, smart TVs, cars, medical devices, and IoT sensors all run Linux-based firmware.
  • Desktop Still ~35% globally, but growing steadily as gaming matures via Steam Proton and desktops like GNOME and KDE Plasma become increasingly polished.

The Philosophy Behind It All

Linux inherits the Unix philosophy write small programs that do one thing well, compose them via pipes, treat everything as a file, and favor transparency over magic. This is why a single Bash one-liner can chain grep, awk, sort, and uniq to process millions of log lines more efficiently than many GUI tools ever could.

It is also why Linux scales: the same kernel powering a Raspberry Pi also powers a 10,000-core HPC cluster. Loadable kernel modules let drivers be added or swapped without recompiling the whole system. The eBPF subsystem lets you safely extend kernel behavior at runtime enabling powerful observability and networking tools without touching kernel code directly.

Unix philosophy in action pipeline example
cat /var/log/syslog | grep "error" | sort | uniq -c | sort -rn

Linux in 2026

The Linux kernel continues its rapid release cadence a new mainline version roughly every two to three months. Key focus areas in 2026 include:

  • Rust integration Writing safer drivers without sacrificing performance.
  • Lazy preemption Improvements for better throughput and responsiveness.
  • Confidential computing Support for secure cloud environments.
  • Wayland adoption Modern display management now default on major desktop distributions.

The most popular distribution, Ubuntu 26.04 LTS, ships with GNOME 50, full Wayland-by-default sessions, and TPM-backed disk encryption a signal of how far the Linux desktop has matured.

Why It Matters to Engineers

For software engineers, Linux is not just an OS choice it is the foundation of the modern software stack. Containers (Docker, Kubernetes) are built on Linux kernel primitives:

Core Linux primitives behind containers
cgroups     # Resource limits per process group
namespaces  # Isolation: PID, net, mount, user
seccomp     # Syscall filtering for sandboxing

Most CI/CD pipelines run on Linux. Most production systems you deploy to run Linux. Understanding the kernel how the scheduler allocates CPU time, how mmap manages virtual memory, how system calls cross the user/kernel boundary directly translates to writing faster, more reliable software.

Takeaway: Linus Torvalds’ “just a hobby” project turned out to be the invisible infrastructure of the digital world. Whether you write code, deploy services, or manage servers you are already running on Linux.
Linux / Git Basic / How to Set Git Username and Email Correctly
Git Basic

How to Set Git Username and Email Correctly

Before your first commit, Git needs to know who you are. Here is how to set your global username and email, verify them, and make sure your commits are linked to your account.

git config Username Email Global Settings GitHub

Step 1 Set Your Username

Run the following command, replacing the example name with your actual name:

Set global username
git config --global user.name "Your Name"

Verify it was set correctly:

Verify username
git config --global user.name
Git username config terminal output

Step 2 Set Your Email

Run the following command, replacing the example address with your actual email:

Set global email
git config --global user.email "your-email@example.com"

Verify it was set correctly:

Verify email
git config --global user.email
Git email config terminal output

Set Both at Once

You can run both commands back to back to set up your identity in one go:

Set username and email
git config --global user.name "Your Name"
git config --global user.email "your-email@example.com"

Verify All Global Settings

To see your full Git configuration at once:

List all settings
git config --global --list
Tip: Use the same email address you have registered on GitHub, GitLab, or Bitbucket so your commits are properly linked to your account.