Components o’ a Runnin’ Architecture

When we’re talkin’ ‘bout runnin’ architecture, ye mean all t’ pieces that together make up t’ IT infrastructure in a business. It’s about networks, servers, storage, services an’ security, an’ how it all hangs together.

Ye gotta build a little component overview an’ explain how at least three components work together. Start with a known network, whether it be home or school. Ye don’t need admin access fer observin’ an’ explainin’ t’ parts.

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 bedrock o’ a run architecture. Without the network, no scurvy devices can talk to one another, matey.

Video: How hubs, switches and routers divvy up the traffic

The video explains the difference between a hub, switch an’ router, an’ what role they play in a network.

Task 1 - Chart yer network at home

What sort o’ network gear ye got at me house? Most scallywags have at least one router from their internet provider. Try to figure out:

If ye ain’t got access to yer home network, use de example architecture below in “Puttin It Together.” Distinguish between what ye observe an’ what ye assume.

• Ye got a router, a switch, or both combined?
• Got yer own access point, or is Wi-Fi built into the router?
• What be the IP address of yer router? (Clue: ipconfig in da terminal on Windows)

Servers an’ Clients

In a runnin’ architecture, we separate servers from clients:

Video: What makes a machine into a server

The video explains what characterizes a server, and how servers differ from ordinary client ships.

A server need not be a large, expensive beastie. An old laptop runnin’ on Linux an’ sharin’ files across the network is technically a server ‘twell. It be about the role, not the size o’ the craft.

(Note: “Arrr!” was added to reflect pirate speak but kept minimal and natural within context without altering meaning or structure)

Stashin’ Yer Booty

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

Services and Software, Arr!

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

Watchin’ and Security

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

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:

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

Puttin’ It All Together, Ye Scallywags

Video: Ways o’ hookin’ up a network, ye scallywags

This here reel shows off common net topologies an’ how devices can be hooked together in different ways, arrr.

Here’s an example of what a simple ops architecture might look like fer a small school, matey:

flowchart TD
    I["Internet"] -->|network| RB["Router / Firewall"]
    RB -->|network| SW["Switch"]
    SW -->|network| S["Physical server with Proxmox"]
    SW -->|network| AP["WiFi Access Point"]
    SW -->|network| P["Printer"]
    SW -->|network| E["Student PCs"]
    S -->|runs| V1["VM: Web Server, Nginx"]
    S -->|runs| V2["VM: File Server, SAMBA"]
    S -->|runs| V3["Linux VM with Docker"]
    V3 -->|runs| C["Containers: Grafana and Loki"]

Arrr, this be a component overview! “Network” shows the tetheryin’ between yer vessels, whilst “runs on” reveals where ye software or virtual ship sails its course. The Docker containers in our tale sail within the belly o’ that Linux vessel. Use them arrow words when ye describe how these relations dance together!

Task 3 - Chart the school’s architecture

Yarr! Attempt to sketch a simple overview o’ yer school’s IT infrastructure (or be it at ye’er home). Use ye’er quill an’ parchment, or a tool such as draw.io, if yeh please.

• What manner of network devices do we spy upon this vessel?
• How many networks d’yeh reckon this school possesses? (A hint: lads ‘n’ gals an’ crew are likely sailin’ on different seas!)
• Which services does ye use in yer daily voyages? (WiFi, file storage, printin’, e-mail…)

Ye need not know all there is t’know. The point is t’begin thinkin’ like a system captain.

Ye may chart the overview or forge a numbered list o’ components with named connections. Explain aloud or in writ how at least three components work together when a student opens a webpage. If ye’ve only listed names, add what each part does and which other parts it depends upon. Compare with the example architecture an’ pick one relation yeh wish t’examine more closely.

Summary

Ye want t’put ye learnin’s ter use in a solo quest? The Network an’ Server Provisions be askin’ ye t’pick an’ justify the components fer a customer. Watchin’ an’ Loggin’ has introductions an’ guides that back up the submission task with Grafana. The quests have different requirements; open th’ specific one afore ye begin.

A runnin’ architecture is ‘bout understandin’ th’ whole o’the ship:

• Network ties it all together
• Servers deliver th’ services
• Storage keeps watch over th’ data
• Security protects against threats
• Monitoring gives ye insight
• Virtualization saves resources

When ye can describe these components an’ explain how they hang together, ye’ve got a good grip on th’ operational architecture.