Pieces o' the ship's engine room,

Skip to content

Avast ye! This be a machine-translated text, an’ it may contain errors, aye!

When we be speakin’ o’ runnin’ architecture, we mean all the parts that together make up a company’s IT infrastructure. ‘Tis be about networks, servers, storage, services, an’ security, an’ how it all be hangin’ together.

What be a Runnin’ Architecture?

A runnin’ architecture be a chart o’ all the IT components in a realm, an’ how they be linked together. Think o’ it as a map o’ the whole IT system. It includes everythin’ from physical hardware to software an’ security measures.

For a small crew, this could be as simple as a router, a server, an’ a few PCs. For a larger vessel, it could include hundreds o’ servers, multiple networks, cloud services, an’ much more.

Network Components

The network be the very foundation o’ a runnin’ architecture. Without the network, no devices can communicate, aye.

Component What it does Example
Switch Connects devices together in a local network (LAN) Unifi Switch, TP-Link
Router Sends traffic between different networks Yer home router, ISP router
Gateway The entry point between yer 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

How does it all be linked, matey?

A typical course o’ the voyage be:

Internet → Router/Gateway → Firewall → Switch → Vessels (PCs, servers, APs)

The switch ties all the crew together internally, and the router/firewall guards what comes in and sets sail out.

Easy Task 1 - Chart Yer Home Network

What manner o’ networkin’ gear do ye have in yer hold? Most scallywags have at least a router from their internet provider. Try to find out:

  • Do ye have a router, a switch, or a combination o’ both?
  • Do ye have a separate access point, or be WiFi built into the router?
  • What be the IP address o’ yer router? (Hint: ipconfig in the terminal on Windows)

Servers and Clients

In a ship’s architecture, we divide ‘tween servers and clients:

Role Description Example
Server A vessel that offers services to others Webserver, file server, print server
Client A vessel that uses the services the server offers Yer PC, mobile, tablet

A server needn’t be a massive, pricey vessel. An old laptop runnin’ Linux and sharin’ files across the network be, technically speakin’, a server. ‘Tis all about the role, not the size of the booty.

Formfaktorer

Servers be found in different physical shapes:

  • Tower - Looks like a regular desktop PC. Good for small crews.
  • Rack - Mounted in a server cabinet (rack). The standard for big data ports.
  • Blade - Compact modules tucked into a chassis. Used in the grandest data ports.

Stashin’ Yer Booty

Data must be stashed somewhere, aye. In a proper ship’s layout, there be several options:

Type Explanation Example
Local Chest Stashin’ it directly in the vessel itself SSD, HDD in a PC or server
Network Hold Network stash shared ‘tween all hands Synology, TrueNAS
Dedicated Hold A dedicated stash network for swift retrieval Used in grand ports o’ call
Cloud Stash Stashin’ it with a cloud provider, savvy? OneDrive, Google Drive, S3

NAS vs. SAN

  • NAS (Network Attached Storage) shares booty over the common network. Easy to set up, it be.
  • SAN (Storage Area Network) uses its own, dedicated network for storage. Faster, but more complex, matey.

For most small and medium-sized crews, NAS be more than enough.

Services and Software, Arr!

The vessels in a fleet architecture be runnin’ various services. Here be some common ones:

Service What it be doin’ Example
E-mail and collaboratin’ Communication and workin’ together Microsoft 365, Google Workspace
File servers Stashin’ and sharin’ booty internally SharePoint, SAMBA
Web servers Deliverin’ web pages to the crew Nginx, Apache
Print server Sharin’ printers ‘tween the ships CUPS (Linux), Windows Print Server
Software Applications the crew be workin’ with Office, Teams, Visual Studio Code

Watchin’ and Security

To keep a shipshape architecture, we need to know what be happenin’:

Component What it does Example
Loggin’ Server Gathers log data from servers and services Grafana + Loki, Graylog
Watchin’ 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 scurvy-ridden malware Windows Defender, ClamAV
Backup Safe keepin’ o’ data and systems Proxmox Backup, Veeam

Backup be not optional

A good rule o’ thumb be the 3-2-1 rule:

  • 3 copies o’ yer data
  • 2 different storage mediums (e.g. disk + cloud)
  • 1 copy offsite

Easy Task 2 - Be Ye Followin’ the 3-2-1 Rule?

Ponder yer own school files, aye:

  • How many copies have ye o’ yer projects?
  • Be ye usin’ only OneDrive, or have ye some stored locally as well?
  • What happens if ye lose access to yer Microsoft account, eh?

Many a sailor finds they have but one copy. ‘Tis enough ‘til it ain’t, savvy?

Virtualization

Instead o’ havin’ a physical vessel for every single service, we can use virtualization to run many a service on the same hardware:

Technology Explanation Example
Virtual machines (VM) The whole operating system runnin’ on shared hardware Proxmox, VMware
Containers Light, isolated environments for single apps Docker, Podman

Virtualization be one o’ the most vital concepts in modern IT sailin’. It saves space, power, and makes it easier to command the services.

Weighin’ Anchor

Here be an example o’ how a simple operational architecture might look for a small school:

Internet
   │
   ▼
[Router / Firewall]
   │
   ▼
[Switch]──────────────────────────────────┐
   │          │          │                │
   ▼          ▼          ▼                ▼
[Server]  [AP WiFi]  [Printer]    [Elev-PCer]
   │
   ├── VM: Webserver (Nginx)
   ├── VM: File server (SAMBA)
   └── Docker: Grafana + Loki

This here chart shows ye, ‘tis need not be complicated. The point be t’ have a reckonin’ o’ what exists, an’ how ‘tis all connected.

Easy Task 3 - Chart the School’s Architecture

Try yer hand at drawin’ a simple map o’ the IT infrastructure at yer school (or yer own humble abode). Feel free to use quill and parchment, or a tool like draw.io.

  • What networkin’ devices be there?
  • How many networks do ye reckon the school has? (Hint: students and crew be likely on separate networks)
  • What services do ye use daily? (WiFi, file storage, printin’, e-mail…)

Ye needn’t know it all. The point be to start thinkin’ in systems, aye.

Summary

A runnin’ architecture be about understandin’ the whole shebang:

  • The Network connects it all, aye
  • Servers deliver the goods and services
  • Storage holds onto the treasure, the data
  • Security protects ye from scoundrels and threats
  • Monitorin’ gives ye a good look-see
  • Virtualization saves ye resources, it does

When ye can describe these parts and explain how they work together, ye’ve got a good grasp o’ the runnin’ architecture.