SSD - Flash, No Moving Parts

Every slow thing about an HDD traced back to one cause: it has to physically move to your data. So - what if we got rid of the moving parts entirely? That question is the solid-state drive, or SSD. "Solid-state" literally means "no moving mechanical parts," and removing the arm and platter changes everything.

What's actually inside

An SSD stores data in flash memory - silicon chips full of microscopic cells, each holding an electrical charge that represents your bits. No platter, no head, no arm. Reading means electronically addressing the cell that holds your data; writing means changing its charge. Nothing physically travels anywhere.

📝 Terminology. The flash inside almost every SSD is NAND flash (NAND is the type of logic gate the cells are built from - you need the name, not the electronics). A small onboard computer, the controller, manages the chips: where data goes, where everything is, and the housekeeping below.

   HDD (Phase 1)                        SSD (this phase)

   ┌──────────────────┐                 ┌──────────────────────────┐
   │  ════ platter ═══ │ spins           │ [chip][chip][chip][chip] │ ← NAND flash
   │  ──── head ────── │ + moves         │ [chip][chip][chip][chip] │   (no motion)
   └──────────────────┘                 │      ┌────────────┐      │
   reach data = move arm,               │      │ controller │      │ ← finds any cell
   wait for spin (slow)                 │      └────────────┘      │   electronically
                                        └──────────────────────────┘

Why random access stops hurting

On an HDD, scattered data was expensive because the head had to travel to it. On an SSD there is no travel: reaching cell #5 and cell #5,000,000 takes essentially the same tiny amount of time, because the controller addresses them electronically. The single most important fact about SSDs: the seek time and rotational latency from Phase 1 are gone - that category of cost doesn't exist when nothing moves.

   Reading 100 scattered little files:

   HDD:  seek+spin+read · seek+spin+read · seek+spin+read · …  (slow, every time)
   SSD:  read·read·read·read·read·read·read·read·read·read·…   (no seek, no spin)

Booting and launching apps - thousands of small scattered reads, the workload that made an HDD crawl - is precisely what an SSD demolishes. Random access on flash isn't a little faster than a spinning disk; it's a different class entirely. Sequential reads are faster too, but the random-access difference is the one you feel day to day.

💡 Key point - this is why an old machine "feels new" with an SSD. Swap an HDD for an SSD in an aging laptop and people describe it as the single biggest speedup they've ever felt - boot, login, opening apps, all snappy. Same CPU, same RAM; what changed is that every operation secretly waiting on a moving arm now isn't. The computer was rarely slow at thinking; it was slow at fetching.

The trade-offs (the real part)

An SSD isn't strictly better than an HDD on every axis. Two real costs:

1. Cost per gigabyte. Flash is more expensive per gigabyte than spinning platters. The gap has narrowed, but the same money still buys substantially more HDD capacity than SSD capacity - which is why the practical sweet spot is often both: a small fast SSD for the OS and apps, a large cheap HDD for bulk files.

2. Flash cells wear out. A cell can only be rewritten a limited number of times before it stops holding a charge reliably. Reading doesn't wear it; writing does. Left naïve, a drive that kept rewriting the same cells (a frequently-updated file, say) would kill them while the rest of the drive sat untouched.

📝 Terminology. Wear-leveling is how the controller solves this: instead of repeatedly writing the same physical cells, it spreads writes evenly across all the cells, so they age together rather than a few dying early. You never see this happening - the controller quietly remaps where data physically lives.

   Without wear-leveling:            With wear-leveling:
   ████░░░░░░░░░░░░░░░░               ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
    ↑ same cells hammered             writes spread across all cells,
      to death, rest unused           so the whole drive ages evenly

⚠️ Gotcha - don't defragment or "optimize" an SSD. Defragmenting exists to make an HDD's head travel less. An SSD has no head, so it buys nothing - and worse, it's a giant pile of writes, the one thing that actually wears flash. Modern operating systems know this and won't defrag an SSD; instead they run a maintenance command called TRIM, which tells the drive which blocks are no longer in use so it can keep write performance high. Let the OS handle it; don't run old HDD-era "optimizers."

How worried should you actually be about wear? For normal desktop and laptop use: not very. With wear-leveling spreading the load, a typical SSD comfortably outlasts the useful life of the computer it's in. Wear becomes a genuine planning concern mainly in write-heavy server scenarios (busy databases, logging, video capture), where drives are chosen specifically for high write endurance. Understand the mechanism; don't lose sleep over it.

Recap

1. An SSD stores data in flash (NAND) cells with no moving parts - a controller addresses any cell electronically.
2. Because nothing moves, seek time and rotational latency are gone, so random access is dramatically faster than an HDD - that's the speedup you feel when booting and launching apps.
3. Trade-off one: flash costs more per gigabyte, so SSD + HDD together is often the smart split.
4. Trade-off two: cells wear out with writes, but wear-leveling spreads writes so the drive ages evenly - rarely a worry for everyday use. Don't defragment an SSD; let the OS run TRIM.

One more twist almost nobody tells you: even with all this flash speed, your SSD can still be held back - not by the flash, but by the cable it plugs into. Next phase.

Watch it animated: SSD vs. HDD

← Phase 1: HDD - Spinning Rust · Guide overview · Phase 3: NVMe vs SATA →