DEV Community

Aisalkyn Aidarova
Aisalkyn Aidarova

Posted on

What is a Computer?

A computer is an electronic machine that:

  1. Accepts input
  2. Processes data
  3. Stores information
  4. Produces output

In simple words:

Input → Process → Output → Storage

As a DevOps engineer, you must understand how a computer works because all your tools (Linux, Docker, Kubernetes, Jenkins, AWS, Terraform) run on computers — either physical servers or cloud virtual machines.


1️⃣ Central Processing Unit (CPU)

Image

Image

Image

Image

What it is:

The CPU (Central Processing Unit) is the brain of the computer.

What it does:

  • Executes instructions
  • Performs calculations
  • Runs programs
  • Handles logic operations

Important CPU Terms:

  • Cores – number of parallel processors
  • Threads
  • Clock speed (GHz)

Why DevOps must know:

  • When your Kubernetes pods are slow → check CPU usage
  • When EC2 instance type changes → CPU count matters
  • When CI/CD builds are slow → CPU limitation
  • Performance tuning in production

2️⃣ RAM (Memory)

Image

Image

Image

Image

What it is:

RAM (Random Access Memory) is temporary memory.

What it does:

  • Stores running programs
  • Stores active processes
  • Clears when system shuts down

Why DevOps must know:

  • Docker containers need memory
  • Kubernetes pods require memory limits
  • Out of memory = application crash
  • JVM apps (Java) depend heavily on RAM
  • kubectl top pod shows memory usage

3️⃣ Storage (Hard Drive / SSD)

Image

Image

Image

Image

What it is:

Permanent storage.

Types:

  • HDD (slow, mechanical)
  • SSD (fast)
  • NVMe (very fast)

What it does:

  • Stores OS
  • Stores files
  • Stores logs
  • Stores databases

Why DevOps must know:

  • EBS volumes in AWS
  • Persistent volumes in Kubernetes
  • Log storage
  • Disk full = production outage
  • IOPS matters for databases

4️⃣ Motherboard

Image

Image

Image

Image

What it is:

Main circuit board connecting all components.

What it does:

  • Connects CPU, RAM, Storage
  • Handles communication between hardware

Why DevOps must know:

  • In cloud → physical server has motherboard
  • Understanding hardware helps in performance troubleshooting

5️⃣ Power Supply Unit (PSU)

Image

Image

Image

Image

What it is:

Converts electricity into usable power.

Why DevOps must know:

In data centers:

  • Power failure = downtime
  • High availability = redundant power supply

Cloud providers handle this, but DevOps must understand infrastructure basics.


6️⃣ Network Interface Card (NIC)

Image

Image

Image

Image

What it is:

Hardware that connects computer to network.

What it does:

  • Sends/receives data
  • Connects to internet

Why DevOps must know:

  • Load balancers
  • VPC networking
  • Security groups
  • IP addresses
  • Latency troubleshooting

Without networking knowledge → no DevOps.


7️⃣ Operating System (Software Layer)

Image

Image

Image

Image

Examples:

  • Linux (Ubuntu, CentOS)
  • Windows Server
  • macOS

What it does:

  • Manages CPU
  • Manages RAM
  • Manages files
  • Runs applications

Why DevOps must know:

You work mostly with:

  • Linux
  • Bash
  • Systemd
  • Logs
  • Process management

How All Components Work Together

User Input → CPU → RAM → Storage
                 ↓
              Network
Enter fullscreen mode Exit fullscreen mode

Example:
You deploy Docker container:

  • CPU runs container
  • RAM stores container process
  • Storage stores image
  • Network exposes port
  • OS manages everything

Why DevOps Engineers MUST Understand Computer Fundamentals

You are not just writing code.

You manage:

  • Servers
  • Containers
  • Clusters
  • Networks
  • Cloud infrastructure
  • Performance
  • Scaling

If you don't understand:

  • CPU → you can't debug high load
  • RAM → you can't fix OOMKilled
  • Disk → you can't fix "No space left on device"
  • Network → you can't fix 503 errors
  • OS → you can't troubleshoot services

Real DevOps Example

Kubernetes pod crashes.

You check:

kubectl describe pod
Enter fullscreen mode Exit fullscreen mode

You see:

OOMKilled
Enter fullscreen mode Exit fullscreen mode

That means:

  • RAM exhausted
  • Not coding problem
  • Infrastructure problem

If you don't understand RAM → you cannot fix production.

Top comments (0)