Skip to main content

The HiSSS of Infrastructure - Part 1

Over the course of my career, I've come to specialize more on a portion of Information Technology called infrastructure. Namely, the underlying support systems that allow all of the cool internet based services we know and love, to flourish and operate without a second thought. These support systems consist not only of physical hardware, such as servers, switches, routers, storage arrays, and so on, but also of the support software that drives these physical systems. Often that includes things such as application servers, proxy servers, network device operating systems, and various shared applications such as e-mail, messaging, and workflow management. Although in the case of most shared software, a team outside of infrastructure manages the application from a user perspective, infrastructure often takes the lead in managing upgrades, software patches, and physical implementation design.

The method that is used to manage these types of systems are varied, and depend greatly on the situation as well as personal philosophy. As a liberal arts technologist, the 'philosophy' behind how you do something has great value to me, so I'm going to spend some blog posts outlining my philosophy of infrastructure management. In that same liberal arts vein, I've come up with an acronym for my philosophy which I call the HiSSS of infrastructure.
  • Highly Available
  • Stable
  • Scalable
  • Secure
In this first installment, we're going to talk about High Availability. Simply put, in non-technical terms, a system is highly available if it is always available when it is expected to be. High availability doesn't just apply to large infrastructures, but to things in our everyday life. We expect our cars, alarm clocks, refrigerators, air conditioners, etc., to all be highly available. We want them to be running when we expect them to be running, without question. Just like when our air conditioner suddenly refuses to fire up at the start of summer, we get just as upset when our computer systems, such as Facebook, e-mail, or Google, suddenly disappear. We have a high expectation of when we want these systems available for our use, so lots of smart people, spend a lot of time and money to make sure that these infrastructures are highly available. 

So how are systems made highly available? One of the most common methods in infrastructure management is called redundancy. Very simply, you never have just one piece of hardware doing a single function. You always duplicate things, so that if one piece of hardware or software malfunctions, you can seamlessly switch over to another system. Unlike our houses where we don't have multiple washing machines, or multiple furnaces, most infrastructures are built on the basic premise that redundancy will be built in to every single facet of the system. You never want to have one single point of failure if at all possible. Redundancy is such a basic fact of infrastructure management that it gets applied down to the level of multiple power supplies, multiple network interfaces, and so on, inside a single piece of server hardware. 

Although having perfect redundancy is great, there are times when systems have to be brought down for various reasons. Hardware maintenance as well as software upgrades are one example of situations where a system might be removed from a highly available pool. Another aspect of infrastructure management and high availability goes beyond physical hardware, to developing a set of policies and procedures to ensure that when a system is taken out of service, it isn't noticed. Being 'invisible' is another key factor in high availability. A primary motivator in any infrastructure management plan is to never be seen unless you have to be.

At one employer, we utilized a system of multiple independent application servers to achieve invisibility. Since we had 3-4 machines serving the public at any one time, we could pull one out of service for a hardware or software upgrade, and then rotate it back in to service when it was completed, continuing the process for all the systems in the pool. This allowed us to do even large software upgrades with almost no disruption to the end users. That meant better service to the customers, and happier management.

A sister concept to invisibility is the notion of segmentation. One of the reasons that we were able to maintain such invisibility, was because we could often pull out and replace just small portions of the systems at a time. By choosing to modularize many of our systems, it allowed for upgrades that were often small and very isolated to one single function of the system. This type of segmentation doesn't always come cheap, and takes a very strong architectural design to implement, both from an infrastructure perspective as well as an application development one. However, with good segmentation most of a system can survive upgrades and maintenance without even notices things going on in other portions.

Being highly available, with it's goals of redundancy, invisibility, and segmentation means that concepts such as Continuous Deployment and other Agile development and business methodologies are able to happen much, much easier. Many shops talk about wanting to move in these new directions, but many times you need to first establish a solid foundation before you can build the mansion. High availability is one pillar in that foundation.


Popular posts from this blog

The beat goes on

Yesterday Apple revealed their long awaited entry into the streaming music field. They were able to do this quickly because of the acquisition of Beats last year, and the systems and intellectual property that came with that purchase. Considering that the music reveal was pretty much the only big news out of a pretty benign developer keynote, I'll take a few moments to talk about what I think about it. Apple was perhaps the defining company in the music revolution of the past 20 years. With the introduction of the iPod that revolutionized portable music, to the creation of the iTunes store and the eventual death of DRM, Apple has been at the forefront of digital music. This leadership comes with high expectations to continue to lead, and so many people have long questioned Apple not getting into the streaming music business quicker. For the past few years new companies have come forth to lead the change in the streaming music evolution. From Pandora and its ability to create un

Microsoft Surface Pro 3

So I've been a horrible blog author and have neglected this site for far to long. It's not that I haven't had anything to say, I've just neglected to say it. So with an attempt to get back on the wagon, here's some thoughts on Microsoft's announcement yesterday for it's Surface Pro 3. Despite being a minor Apple fanboy, the most interesting company to watch, in the personal computing space right now, is Microsoft. With the departure of Steve Ballmer, and the rise of Satya Nadella, it has been an interesting 9 months for one of the founding pioneers of personal technology. Many agree that Windows 8 has not lived up to what Microsoft would like it to be. They made a bold attempt to redefine how users interact with their computers, and merge the tablet and desktop experience. However, that experiment, by most accounts, has failed. This is a common pattern for Microsoft however, alternating between a mediocre OS release, and then a stellar one. Therefore, it&#

The Great Experiment

Recently, a tech journalist that I've followed for many years, and who is an Apple fanboy, posted a series talking about why he switched from an iPhone to an Android phone . It's a good read, and worth the time to see why he made the decision he did. Since I have a Verizon Galaxy Nexus sitting on my desk as a Wi-Fi device, I thought, "What the heck, let's give this a go for a week." So for the past week I've shelved my trusty iPhone 5 and have delved deep into the world of stock Android 4.1. So in the spirit of "copying is the sincerest form of flattery" here's my write-up of my experiences with Google's mobile OS. First, I need to make one caveat. After using the Nexus for a week I have to say that I do NOT like this device. It constantly loses 4G signal, and the battery life almost makes it unusable. I could barely make it to lunch before I was at 20-30% battery. So in the spirit of fairness, if I truly wanted to switch full time to Andro