"Explain the difference between a process and a thread."
Classic interview question. And honestly? It doesn't need a complicated answer.
Let's use an escape room.
The Room Is the Process
You and your friends walk into an escape room you've rented for the hour. That room is your process.
It has its own locked doors, its own puzzles, its own timer. Completely isolated from whatever's happening in the room next door. In software terms, a process is an independent program running in memory, with its own resources and environment. Nothing leaks in or out unless you explicitly allow it.
The Players Are the Threads
Inside that room, there are people — you and your friends. Each one of you is a thread.
Multiple players, same room. Multiple threads, same process.
A thread is a unit of execution within a process. It does the actual work. And because all threads live inside the same process, they share the same memory — the same clues, the same variables, the same space.
That's what makes threads fast. No overhead, no inter-process handshaking. One thread finds a key, another can use it immediately.
The Catch
Here's where the analogy earns its keep.
Imagine one of your friends loses patience and smashes a puzzle box. The staff walks in. Game over. Everyone gets kicked out — not just the person who broke it.
That's the risk with threads. If one thread crashes hard enough — unhandled exception, bad memory access, whatever — it can bring the entire process down. All threads included.
Processes don't have this problem. A crash in one process doesn't touch another. The isolation is the point.
So Which Do You Use?
Depends on what you're optimizing for.
Processes give you isolation and stability. Good when you need fault boundaries — when one part of your system failing shouldn't cascade into everything else. The cost is heavier communication between them.
Threads give you speed and shared state. Good when tasks are tightly coupled and need to coordinate fast. The cost is that a poorly written thread can ruin the party for everyone.
Most real systems use both — multiple processes for isolation, multiple threads within each for performance.
Processes are separate worlds. Threads are collaborators within the same world.
— Cheers, NP