From Unix Admin to Technologist: Evolving Network Architectures 1991 and Today

In 1991/2, I was a Unix System Administrator at Cigna FIRST, an innovative force-place insurance company in Irvine, California. The technology landscape was rapidly evolving, and I navigated this complex environment without a formal college degree. In an industry where credentials often carried significant weight, I knew I had to stand out in other ways to secure my future.

My mission was clear: I needed to understand everything—telco systems, Unix, databases, TCP/IP, and the vast array of hardware that powered it all. I wasn’t just focused on the "how" and the "why"—the strategies that made technology effective and the broader context in which it operated. I attempted to utilize every spare minute except for a few nights of the week when I would spend an hour and get a bowl of "Hobo Rice," the cheapest (~$3) item, at the Harbour House Cafe in Dana Point.

This journey was about more than just securing my current role or climbing the corporate ladder. It was about ensuring I could find employment easily, anywhere, by being the best candidate. Additionally, I wanted to be prepared for the Sun Advanced System Administration certification if Cigna approved it the following June. To gauge my progress, I interviewed for roles all over Southern California, often driving up to two hours before work in the morning. This was grueling—if it had been just for me, I might have taken it slower. But my motivation extended beyond personal ambition; I was driven by the desire to support my partner and ensure her dreams could flourish alongside mine.

During this time, I developed a simple yet effective way to conceptualize computing resources in the office—a framework that organized the resources into three distinct rings:

1. Ring 1: Data Providers These were the foundational systems that stored and served data across the network, including file servers, database servers, and FTP servers. They represented the network's core, where all essential data and services reside.
2. Ring 2: Compute Servers This ring consisted of servers that consumed resources from the data providers and handled the processing power for the network. These included shell servers, application servers, and terminal servers, serving as the intermediaries between data storage and end-user interaction.
3. Ring 3: End-User Devices The outermost ring contained the devices that end-users interacted with daily, such as PCs, X-Terminals, Sun Workstations, and printers. These devices accessed the resources and compute power provided by the inner rings.

This framework helped organize and manage the network's architecture, making it easier to understand the flow of data and the role each device or server played within the environment. It was particularly useful for planning infrastructure, troubleshooting, and ensuring efficient resource allocation. Compared to today's technology, my first-year concepts as a System Administrator seem entirely outdated and overly simplified.

Reimagining the Three Rings in a Modern Context

Fast forward to today, and the technological landscape has changed dramatically. However, the core principles of building efficient, scalable, and resilient networks remain the same. The "three rings" framework I developed in the early '90s has evolved to fit modern technologies, reflecting the advancements in cloud computing, containerization, and edge processing.

1. Core Layer (Innermost Ring): The core layer has moved to the cloud, hosted by providers like AWS, Azure, and GCP. This layer now contains critical data services, distributed databases, and object storage. Security and redundancy are paramount, with Zero Trust and SDN policies ensuring controlled access and resilience. The principles that guided the original Ring 1 are still relevant, but they now manifest through scalable, high-availability cloud platforms.
2. Compute Layer (Second Ring): This layer has now transformed into containerized applications running on Kubernetes clusters, either in the cloud or at the edge. Edge computing devices also reside here, processing data locally before syncing with the core. This evolution reflects the shift from centralized processing to a more distributed, dynamic approach, where compute power is deployed closer to where it's needed, reducing latency and improving performance.
3. Endpoint Layer (Outer Ring): The endpoint layer now includes Virtual Desktop Infrastructure (VDI) instances and various endpoint devices managed by Unified Endpoint Management (UEM). These devices are the user-facing interfaces of the network, connecting users to the power of the core and compute layers. The devices have become more diverse and powerful, but their role in the network remains similar to what it was in the early '90s—providing access to the underlying infrastructure.

Networking: SDN and Zero Trust Architecture

Networking has also evolved, with Software-Defined Networking (SDN) and Zero Trust Architecture now playing crucial roles in managing and securing the flow of data between these layers. These technologies ensure that data is accessible only to authorized users and devices, maintaining the security and integrity of the network.

Data Layer: Distributed Databases and Object Storage

The data layer, once confined to physical servers in a data center, has expanded to include distributed databases and object storage in the cloud. This shift has allowed for greater scalability and resilience, enabling organizations to handle vast amounts of data across multiple locations.

Monitoring and Automation: Observability and Infrastructure as Code

Modern networks are monitored and managed through observability tools and Infrastructure as Code (IaC) practices. These allow for real-time insights into the performance and health of the network, as well as automated management and scaling of resources, further enhancing the resilience and efficiency of the infrastructure.

DevOps Practices: Continuous Integration/Continuous Deployment (CI/CD)

The adoption of DevOps practices, particularly CI/CD, has revolutionized the way software is developed and deployed. This approach ensures that new features and updates can be delivered rapidly and reliably, aligning with the dynamic nature of modern networks.

Conclusion: The Evolution of a Framework

Reflecting on this journey, it becomes clear that while technology has evolved dramatically, the core principles of building efficient, scalable, and resilient networks remain the same. The "three rings" framework I developed in the early '90s has found new life in today’s cutting-edge technologies, allowing us to create infrastructures that are not only powerful but also flexible enough to adapt to whatever the future holds.

This journey has taught me that while degrees and credentials can open doors, it’s the relentless drive to understand, innovate, and adapt that truly builds a career. In a world where technology evolves faster than ever, this mindset isn’t just valuable—it’s essential.