Akins IT Named to Best Places to Work in Orange County 2020

Akins IT • October 29, 2020

We are proud to announce that Akins IT was recently named as one of the 2020 Best Places to Work in Orange County, ranking #16 in the Small Employer Category. The awards program was created in 2009 and is a project of the Orange County Business Journal and Best Companies Group.

This county-wide survey and awards program was designed to identify, recognize and honor the best places of employment in Orange County, California, benefiting the county's economy, its workforce and businesses.

To be considered for participation, employers had to fulfill the following eligibility requirements:

Have at least 15 employees working in Orange County;
Be a for-profit or not-for-profit business or government entity;
Be a publicly or privately held business;
Have a facility in Orange County; and
Must be in business a minimum of 1 year.

Organizations from across the county entered the two-part process to determine the Best Places to Work in Orange County. The first part consisted of evaluating each employer's workplace policies, practices, and demographics. This part of the process was worth approximately 25% of the total evaluation. The second part consisted of an employee survey to measure the employee experience. This part of the process was worth approximately 75% of the total evaluation. The combined scores determined the top organizations and the final ranking. Best Companies Group managed the overall registration and survey process in Orange County and also analyzed the data and used their expertise to determine the final ranking.

< Older Post

Newer Post >

AWS stumbled this morning. Here’s why multi‑cloud keeps you moving.

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.)