Skip to main content

Who's the boss?

I recently sent an email at work, that talked a lot about some of the more academic sides of "infrastructure". Particularly the notion of where infrastructure gets it's direction and workload from. So I thought I'd share a few of those thoughts here.

Infrastructure is a bit of a weird beast. It's a foundational piece of any technology deployment, but in most cases it isn't the "focus" of the deployment. Infrastructure is both independent-yet-dependent. It stands at a crossroads between two distinct worlds.

First, infrastructure is independent, in the sense that it is agnostic. It can be built in a similar fashion if you're deploying a bookstore, financial application, music player, or blog. There are general concepts, principles and tactics (see The HiSSS of Infrastructure series...) that are universal to whatever application you are building and deploying. So by that standard, infrastructure is a thing unto itself.

But yet, infrastructure is nothing by itself. It's the foundation upon which cool things are built. Without an application or service being deployed upon it, it's pointless. So therefore infrastructure is dependent upon being "used" by something greater than itself. It's purpose is fulfilled by being used.

So there are three main areas in which infrastructure takes it's direction.

  1. Internal - There are things that infrastructure needs to do, to maintain itself and keep functioning. Things like security updates, hardware maintenance and general design updates, all come from initiatives internal to itself. There is a cadre of work that is built on these internal pressures. 
  2. Future-forward - The second area usually comes from a development team, and revolves around planning for the future. Investing in new technologies and their foundational pieces is a key part of infrastructure's work. People always have a million good ideas, and they need a solid foundation to make them reality.
  3. Reactive/Preventative - This stream of work comes from the discovery of issues that need to be addressed in the infrastructure. Service issues, capacity management, and general problem resolution are the third key workstream for a strong base.
These three areas make up the scope of work that an infrastructure team works on, and understanding and working within a fully agreed understanding of the importance of foundation, and building a house on solid ground, always benefits an entire initiative. 

Comments

Popular posts from this blog

I love typing on my iPad

Ok, before you think I've gone crazy and suddenly believe I like smacking away at a non-responsive touch-screen, let me clarify that title... "I love typing on my bluetooth keyboard on my iPad." Like many people, I took the plunge and got a wireless keyboard for my iPad, because for any serious typing work, you really can't beat the smooth responsiveness of the Apple Wireless keyboard. But, just to clarify things further, it's not the bluetooth keyboard that is the reason I love typing on my iPad. Let's correct that title one more time... "I love writing on my bluetooth keyboard on my iPad." There we go, that's better, and it gets to the heart of what I wanted to share in this post. I'm going to make a bold statement, which I'm sure tons of people will find issue with, but here is it. The iPad is a perfect writing tool. Ya, that's right. I just said that a small 10 inch device that you need to purchase an additional keyboard for

The NEW Microsoft

Today Microsoft held their Build conference keynote. As with Apple and Google, developer conference keynotes have become a mainstay of announcements for the general public beyond developers. At first it seemed that Microsoft would be bucking that trend today as the first portions of their keynote were very, very developer centric. However, a lot changed when they started talking about Windows 10. Microsoft is betting the future on building a platform that applications will build off of. Much like Apple and Google, they seem to be discovering that the real money isn't in the operating system itself, but in helping bring applications to consumers through validated app stores. In Microsoft's case it's also seeking to converge all of their platforms into a single unified platform. They once again reiterated today that Windows 10 will run on all of the devices that are out there, from phones to tablets to PC's to XBox game consoles. This means that applications can be writ

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