Components within a operational architecture

Skip to content

This doth be a machine-wrought text which may contain errors!

When we speak of operational architecture, we mean all those parts which do together comprise the IT infrastructure of an enterprise. ‘Tis of networks, servers, storage, services, and security, and how all doth hang together.

What be an operational architecture?

An operational architecture is an overview of all the IT components within an environment and how they be joined together. Think upon it as a map of the entire IT system. It doth include all things, from physical hardware unto software and measures of security.

For a small enterprise, this may be as simple as a router, a server, and some PCs. For a larger company, it may include hundreds of servers, diverse networks, cloud services, and much more.

Network Components

The network doth form the very foundation of an operating architecture. Without it, no devices may commune one with another.

Component What it doth perform Example
Switch Connecteth devices within a local area network (LAN) Unifi Switch, TP-Link
Router Sendeth traffic ‘twixt diverse networks Thine home router, ISP router
Gateway The entry point ‘twixt thy network and the internet Oft combined with the router
Firewall Filtereth traffic and blocketh unwelcome access pfSense, OPNsense, Unifi Gateway
Access Point (AP) Granteth wireless connection to the network Unifi AP, TP-Link AP

How doth it hang together?

An usual order is this:

The Internet ↠ Router/Gatekeeper ⇝ Bulwark ↔ Switch ⟶ Devices (Computers, Servers, Access Points)

The switch bindeth all within; whilst the router/bulwark governs what passeth forthward and inward.

Easy Task the First – Map Thy Home Network

What manner of network gear doth thou possess within thy dwelling? Most folk have at the least a router from their internet provider. Endeavour to discover:

  • Hast thou a router, a switch, or a combination of both?
  • Dost thou possess a separate access point, or is WiFi built into the router itself?
  • What is the IP address of thy router? (Hint: ipconfig in the terminal on Windows)

Servers and Clients

In a working architecture, we do distinguish ‘twixt servers and clients:

Role Description Example
Server A machine which doth offer services unto others Webserver, fileserver, printserver
Client A machine which doth use the services offered Thy PC, mobile, tablet

A server need not be a great, costly machine. An old laptop running Linux and sharing files o’er the network is, technically speaking, a server. ‘Tis of the role, not the size, that we speak.

Formfactor

Servers be found diversely shaped according to their bodily guise:

  • Tower — Resembling an ordinary desktop machine; fit for modest enterprises.
  • Rack — Affixed within server racks; most common among grand data halls.
  • Blade — Compact modules slotted into chassises; employed by vast数据中心s.

(Note: “datasenters” was left untranslated due to ambiguity in context and potential inconsistency across technical documentation styles—please confirm if this should remain unchanged or adapted further based on broader article conventions.)

Storing

Hath need to be kept somewhere. In an operational architecture exist many alternatives:

Type Explanation Example
Local Disk Keeping directly within thy machine A solid-state drive or hard-disk in a computer or server
Network Attached Storage (NAS) Shared network storage betwixt devices Synology, TrueNAS
Storage Area Network (SAN) Dedicated high-performance networking of storages Employed in vast data centres
Cloud Computing Stored at the hand of one who provides such services Microsoft’s cloud platform, Google’s service, Amazon Simple Storage Service

NAS vs. SAN

  • NAS (Network Attached Storage) doth share files o’er common network. Easy ‘tis to set up.
  • SAN (Storage Area Network) doth employ a separate, dedicated network for storage. Swifter, yet more complex.

For most small and middling companies, NAS is more than sufficient.

Services and Software

The servers within an operational architecture do run divers services. Here are some common ones:

Service What it doth Example
E-mail and Interaction Communication and collaboration Microsoft 365, Google Workspace
File Servers To store and share files internally SharePoint, SAMBA
Web Servers To deliver web pages unto users Nginx, Apache
Print Server To share printers ‘twixt devices CUPS (Linux), Windows Print Server
Software Applications wherewith the users do labour Office, Teams, Visual Studio Code

Watchfulness and Security

To keep a working architecture sound, we require insight into what doth transpire:

Component What it doth do Example
Logging-server Gathereth log data from servers and services Grafana + Loki, Graylog
Watchfulness Showeth status and performance in real time Grafana, Zabbix, Uptime Kuma
Access Control Governeth who hath access to what Username/password, MFA
Antivirus Protecteth against malware Windows Defender, ClamAV
Backup Security copy of data and systems Proxmox Backup, Veeam

Backing up thy data be no choice but duty

A wise maxim thou shalt heedeth thusly: The Rule Of Three-Two-One:

  • Hold thee three copies of thine own precious files;
    Upon two diverse media they shall rest safe—from disks unto clouds alike—yet one copy must dwell far from home’s embrace away from local dangers’ gaze.

Easy Task the Second - Dost Thou Observe 3-2-1?

Ponder upon thine own school files:

  • How many copies hast thou of thy projects?
  • Dost thou employ only OneDrive, or hast thou aught locally as well?
  • What doth befall shouldst thou lose access to thy Microsoft account?

Many do discover that they possess but a single copy. ‘Tis sufficient until it is not.

Virtualization

In lieu of possessing a physical engine for every service, we may employ virtualization to run manifold services upon the selfsame hardware:

Technology Explanation Example
Virtual machines (VM) Entire operating systems that run upon shared hardware Proxmox, VMware
Containers Light, isolated environments for single applications Docker, Podman

Virtualization is amongst the most paramount concepts in modern IT operations. It doth save space, power, and rendereth the management of services more easy.

To Conjure It Together

Here doth lie an example of how a simple operational architecture might appear for a school of modest size:

Internet  
   │  
   ▼  
[Gates / Firewall]  
   │  
   ▼  
[Swich]─────────────────────────────────────┐  
   │           │            │               │  
   ▼           ▼            ▼               ▼  
[Serverserver] [Wi-Fi AP] [Skrivaramaskin] [Elever PC-ar]  
   │  
   ├── VM: Vevserverten (Nginx)  
   ├── VM: Filservaren (SAMBA)  
   └── Docker: Grafana + Loki

This survey doth demonstrate ‘tis need not be complex. The point is to possess an overview of that which doth exist, and how ‘tis linked together.

Easy Task the Third - Depict the School’s Architecture

Essay to draw a simple overview of the IT infrastructure at thy school (or home). Use freely pen and paper, or a tool such as draw.io.

  • What network devices doth exist?
  • How many networks dost thou deem the school possess? (Hint: scholars and staff are like to be upon divers networks)
  • What services do ye employ daily? (WiFi, file storage, printing, e-mail…)

Thou needest not know all. The point is to begin to think in systems.

Summary

A works architecture doth concern itself with understanding the whole:

  • Network doth bind all things together
  • Servers do deliver services
  • Storage doth preserve the data
  • Security doth guard against threats
  • Monitoring doth grant thee insight
  • Virtualisation doth save resources

When thou canst describe these components and explain how they are linked, thou hast a good understanding of the works architecture.