This is a machine-translated text that may contain errors!
When we talk about operational architecture, we mean all the parts that together make up the IT infrastructure of an enterprise. This includes networks, servers, storage, services and security, and how everything connects.
What is an Operational Architecture?
An operational architecture is an overview of all IT components in an environment and how they are connected. Think of it as a map of the entire IT system. It includes everything from physical hardware to software and security measures.
For a small business, this can be as simple as a router, a server, and a few PCs. For a larger organization, it can include hundreds of servers, multiple networks, cloud services, and much more.
Network Components
The network is the foundation of an operational architecture. Without the network, no devices can communicate.
| Component | What it does | Example |
|---|---|---|
| Switch | Connects devices together in a local area network (LAN) | Unifi Switch, TP-Link |
| Router | Sends traffic between different networks | Your home router, ISP router |
| Gateway | The entry point between your network and the internet | Often combined with the router |
| Firewall | Filters traffic and blocks unwanted access | pfSense, OPNsense, Unifi Gateway |
| Access Point (AP) | Provides wireless connection to the network | Unifi AP, TP-Link AP |
Hvordan henger det sammen?
A typical sequence is:
Internet → Router/Gateway → Firewall → Switch → Devices (PCs, servers, APs)
The switch connects everything internally, and the router/firewall controls what goes in and out.
Task 1 - Map Your Home Network
What kind of network equipment do you have at home? Most people have at least a router from their internet provider. Try to find out:
- Do you have a router, a switch, or a combination?
- Do you have a separate access point, or is WiFi built into the router?
- What is the IP address of your router? (Hint:
ipconfigin the terminal on Windows)
Servers and Clients
In an operational architecture, we distinguish between servers and clients:
| Role | Description | Example |
|---|---|---|
| Server | A machine that offers services to others | Web server, file server, print server |
| Client | A machine that uses the services the server offers | Your PC, mobile, tablet |
A server does not need to be a large, expensive machine. An old laptop running Linux and sharing files over the network is technically a server. It’s about the role, not the size.
Formfaktorer
Servers come in various physical formats:
- Tower - Looks like a standard desktop PC. Suitable for small environments.
- Rack - Mounted in a server cabinet (rack). Standard for data centers.
- Blade - Compact modules that are placed in a chassis. Used in large data centers.
Storage
Data must be stored somewhere. In an operational architecture, there are several options:
| Type | Explanation | Example |
|---|---|---|
| Local disk | Storage directly in the machine | SSD, HDD in a PC or server |
| NAS | Network storage shared between devices | Synology, TrueNAS |
| SAN | Dedicated storage network for high performance | Used in large data centers |
| Cloud storage | Storage with a cloud provider | OneDrive, Google Drive, S3 |
NAS vs. SAN
- NAS (Network Attached Storage) shares files over a standard network. Easy to set up.
- SAN (Storage Area Network) uses a separate, dedicated network for storage. Faster, but more complex.
For most small and medium-sized businesses, NAS is more than good enough.
Services and Software
The servers in an operational architecture run various services. Here are some common ones:
| Service | What it does | Example |
|---|---|---|
| E-mail and Collaboration | Communication and collaboration | Microsoft 365, Google Workspace |
| File Servers | Store and share files internally | SharePoint, SAMBA |
| Web Servers | Deliver web pages to users | Nginx, Apache |
| Print Server | Share printers between devices | CUPS (Linux), Windows Print Server |
| Software | Applications that users work with | Office, Teams, Visual Studio Code |
Monitoring and Security
To keep an operational architecture healthy, we need insight into what is happening:
| Component | What it does | Example |
|---|---|---|
| Logging server | Collects log data from servers and services | Grafana + Loki, Graylog |
| Monitoring | Shows status and performance in real time | Grafana, Zabbix, Uptime Kuma |
| Access control | Controls who has access to what | Username/password, MFA |
| Antivirus | Protects against malware | Windows Defender, ClamAV |
| Backup | Backup of data and systems | Proxmox Backup, Veeam |
Backup er ikke valgfritt
A good rule of thumb is the 3-2-1 rule:
- 3 copies of your data
- 2 different storage media (e.g. disk + cloud)
- 1 copy offsite
Task 2 - Do you follow 3-2-1?
Think about your own school files:
- How many copies do you have of your projects?
- Do you only use OneDrive, or do you have something locally as well?
- What happens if you lose access to your Microsoft account?
Many find out that they only have one copy. That works until it doesn’t.
Virtualization
Instead of having a physical machine for each service, we can use virtualization to run multiple services on the same hardware:
| Technology | Explanation | Example |
|---|---|---|
| Virtual Machines (VM) | Entire operating systems running on shared hardware | Proxmox, VMware |
| Containers | Lightweight, isolated environments for single applications | Docker, Podman |
Virtualization is one of the most important concepts in modern IT operations. It saves space, power, and makes it easier to manage services.
Putting it Together
Here is an example of what a simple operational architecture might look like for a small school:
Internett
│
▼
[Ruter / Brannmur]
│
▼
[Switch]──────────────────────────────────┐
│ │ │ │
▼ ▼ ▼ ▼
[Server] [AP WiFi] [Printer] [Elev-PCer]
│
├── VM: Webserver (Nginx)
├── VM: Fileserver (SAMBA)
└── Docker: Grafana + Loki
This overview shows that it doesn’t need to be complicated. The point is to have an overview of what exists, and how it all connects.
Task 3 - Draw the Architecture of the School
Try to draw a simple overview of the IT infrastructure at your school (or at home). Feel free to use pen and paper, or a tool like draw.io.
- What network devices exist?
- How many networks do you think the school has? (Hint: students and staff are likely on different networks)
- What services do you use daily? (WiFi, file storage, printing, email…)
You don’t need to know everything. The point is to start thinking in systems.
Summary
An operational architecture is about understanding the whole:
- Network connects everything
- Servers deliver services
- Storage safeguards the data
- Security protects against threats
- Monitoring provides insight
- Virtualization saves resources
When you can describe these components and explain how they relate to each other, you have a good understanding of the operational architecture.