Monolithic vs Microkernel: Which OS Design Is Right for You?

Monolithic Kernel: All Code Runs in Kernel Mode

The simplest approach is to place every piece of kernel code in kernel mode, giving each part full hardware control. The compiled kernel becomes a single binary executable that runs as one large process in a single address space, similar to a complex single‑process application. This design is often called a monolithic kernel.

Because all kernel code shares the same address space, interaction between components is just ordinary function calls, making inter‑module communication straightforward. However, a bug in any kernel module can crash the entire system, requiring a reboot.

Microkernel: Keep Only Core Services in Kernel Mode

To reduce crash risk, a microkernel keeps only essential services (e.g., process creation, messaging) in kernel mode, while other components run as user‑mode servers. User‑mode services communicate via inter‑process communication (IPC) mediated by the kernel.

This separation means that a bug in a user‑mode server (such as a file server) does not bring down the whole kernel. The trade‑off is performance: communication between modules now involves context switches and IPC, which is slower than direct function calls in a monolithic kernel.

请求：应用程序 -> 内核 -> File server
返回：File server -> 内核 -> 应用程序

Real‑World Implementations

Both designs are widely used. Linux and many Unix systems employ a monolithic kernel, while macOS, Windows NT, and Huawei’s Harmony OS are generally considered microkernel‑based (or hybrid). Interestingly, MINIX, which heavily influenced Linus Torvalds, is a microkernel, whereas Linux, derived from it, chose the monolithic approach.