Future Proofing Your Infrastructure

Akins IT • June 30, 2016
Connect with us

A client who is moving into a new office recently asked for advice in setting up his infrastructure. After scoping out the best spot for mounting his server rack, we surveyed the space to get an idea of how he wanted to deploy the data drops. As soon as someone brings up data drops, the next topic is naturally cabling and what type to install. In this situation, our recommendation was to run “Category 6e” cables… but why and what’s the difference between 6e, 6a, and 5e?


 The simple answer to the first half of the question is that whenever you’re installing infrastructure, whether it’s cables, switches, or servers, you always take into consideration the length of time you expect to be using it and plan for likely growth.

However, this still leaves the question, “What’s the difference?”


 Here’s where the answer gets nerdy. The difference in cable categories comes down to a handful of relevant features; specifically, frequency range (MHz), electromagnetic compatibility (EMC), and signal-to-noise margin to name a few. It gets nerdier, but in plain English this means that the higher the grade of cable the more bandwidth it can handle with less interruptions and less potential packet loss.

 From Cat 5e to Cat 6, the frequency range increases from 1-100 to 1-250 MHz. From Cat 6 to 6A, the frequency range doubles to 1-500 MHz. The Telecommunications Industry Association doesn’t actually recognize “6e” as a standard, but the “e” is a naming convention referring to “enhanced” that manufacturers began incorporating to convey the increase in performance.


 So we’re not 100% accurate when we are saying Cat 6e, but unless you want to split hairs feel free to continue… everyone will still know what you mean.

By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts