Operating System Models Overview

Every operating system is built according to a specific architectural philosophy. This internal structure determines how the kernel interacts with hardware, how it manages memory, and how stable it is when something goes wrong.

Choosing an OS model is a fundamental design decision that balances performance, security, and complexity.

In a monolithic design, the entire operating system (scheduling, file systems, device drivers, memory management) runs as a single, massive program in kernel space.

Because everything is in the same address space, communication between components is incredibly fast. However, if any single part of the kernel (like a buggy printer driver) fails, the entire operating system crashes.

Examples: Linux, MS-DOS, traditional Unix.

A microkernel takes the opposite approach. It keeps only the absolute essentials inside the kernel (Inter-Process Communication, basic memory management, and scheduling). Everything else—like drivers and file systems—runs as isolated user-level processes.

If a driver crashes in a microkernel system, the OS survives; you just restart that specific process. The downside is performance, as every request now requires 'Message Passing' between different address spaces.

Examples: Minix, QNX, L4.

Most modern commercial operating systems use a Hybrid approach. They combine the speed of a monolithic kernel with the modularity of a microkernel.

They run critical performance-heavy services in kernel space but keep other parts modular and isolated.

Examples: Windows NT (Windows 10/11), macOS (XNU kernel).

In a layered model, the OS is divided into a number of layers (levels), each built on top of lower layers. The bottom layer (Layer 0) is the hardware; the highest (Layer N) is the user interface.

Each layer only uses the functions and services provided by the layer immediately below it, which makes debugging much simpler.