Not every computer needs the same kind of operating system. A bank’s batch payroll run, a car’s braking controller and a smartphone all have very different needs. The main types of operating systems reflect those needs: some focus on throughput, some on fast response, some on sharing resources across a network.
This guide explains the main types, with real examples and their strengths and weaknesses.

Overview
| Type | Main goal | Examples |
|---|---|---|
| Batch | Process large jobs without user interaction | Early IBM mainframe systems; modern batch schedulers on z/OS |
| Time-sharing (multi-user) | Many users share one system interactively | Unix, Linux servers |
| Distributed | Many machines act as one system | Research systems; ideas used in cloud platforms |
| Network | Share files, printers and users across a network | Windows Server, Linux with Samba |
| Real-time | Respond within strict time limits | FreeRTOS, QNX, VxWorks, Zephyr |
| Mobile | Touch, battery life, sensors, apps | Android, iOS |
| Embedded | Run dedicated devices with limited resources | Embedded Linux in routers and TVs |
| Desktop | Personal productivity | Windows, macOS, Linux desktops, ChromeOS |
1. Batch operating systems
In batch systems, operators group similar jobs and run them one after another without user interaction. Early mainframes worked this way.
- Pros: efficient for large repeated jobs, such as payroll or billing.
- Cons: no interaction while a job runs, and one failed job can delay the queue.
Batch processing still exists, for example in nightly data jobs, but it now runs on general-purpose systems.
2. Time-sharing operating systems
Time-sharing gives each user or process a short slice of CPU time in turn. As a result, many users feel they have the machine to themselves. Unix grew from this idea, and every modern multi-user OS uses it.
- Pros: quick response and fair sharing.
- Cons: more complex scheduling and security between users.
3. Distributed operating systems
A distributed OS manages a group of independent computers so that they appear as one system. Users do not need to know where files or processes actually live.
- Pros: scalability and fault tolerance.
- Cons: complex to build, and network problems affect the whole system.
Pure distributed operating systems remain mostly in research. However, their ideas live on in cluster managers and cloud platforms such as Kubernetes.
4. Network operating systems
A network OS runs on servers and provides shared services, such as files, printers, user accounts and security, to clients over a network. Windows Server with Active Directory is the classic example.
- Pros: central management of users and resources; easy backups.
- Cons: servers become critical points of failure, and they need skilled administrators.
5. Real-time operating systems (RTOS)
A real-time OS guarantees that tasks finish within strict deadlines.
- Hard real-time: missing a deadline is a failure, as in airbags, pacemakers and industrial controllers.
- Soft real-time: occasional delays are acceptable, as in video streaming.
Examples include FreeRTOS, Zephyr, QNX and VxWorks. Linux can also provide real-time behaviour with the PREEMPT_RT features, which were merged into the mainline kernel in 2024.
6. Mobile operating systems
Mobile operating systems are built for touch screens, wireless networks, sensors and long battery life. They also use strong app sandboxing.
- Android, based on the Linux kernel, leads worldwide.
- iOS runs on iPhones and is closely tied to Apple hardware.
7. Embedded operating systems
Embedded systems run inside devices such as routers, smart TVs, cameras and cars. They use small, specialised operating systems, often embedded Linux or an RTOS, with limited memory and storage.
8. Desktop operating systems
Desktop systems such as Windows, macOS, Linux distributions and ChromeOS focus on a rich user interface, broad hardware support and a large range of applications. ChromeOS, for example, is built around the web browser and cloud services, with Linux underneath.
How to choose
- Need guaranteed timing? Choose an RTOS.
- Running shared services for many users? Choose a server or network OS.
- Building a device with limited resources? Choose embedded Linux or an RTOS.
- Running many workloads at scale? Use Linux servers with orchestration, such as Kubernetes.
Related guides
Sources
Running Linux servers in production? Our Linux server hardening & security audit checks configuration, patching, SSH and logging. You can also use our free Linux server hardening checklist, or contact us.
