Welcome!

James Houghton

Subscribe to James Houghton: eMailAlertsEmail Alerts
Get James Houghton via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by James Houghton

In a previous post we discussed the positive shift in the cloud computing discourse towards actionable steps rather than philosophical diatribes on definitions. And to support that discussion we offered the following list of things not to do: Not understanding the business value Assuming server virtualization is enough Not understanding service dependencies Leveraging traditional monitoring Not understanding internal/external costs As we continue our discussion of these missteps, in this post we'll address both a mistake and a common misconception. Cloud computing is not about any particular technology, but rather is a new operational model for the delivery of IT services. Make no mistake: technology and implementation decisions have the potential to radically change your IT financial models by increasing IT efficiency. But this does not mean that specific technolog... (more)

Accounting for the Cloud

The past few weeks we have been discussing some of the mistakes made in early cloud deployments. As a refresher, here are the issues we outlined: Not understanding the business value Assuming server virtualization is enough Not understanding service dependencies Leveraging traditional monitoring Not understanding internal/external costs This week we are discussing a key mistake that occurs fairly often; one that only manifests long after the solution is operational...blindly assuming that Cloud equals costs savings. Blasphemy, you say - how could it possibly not cost less? Let's t... (more)

Who Really Needs a Blueprint?

A few days ago we facilitated a passionate discussion on the subject of Blueprints (ah, the joys of an emerging market). The gist of the conversation was focused on deciding where limited marketing resources should be applied, and during that exercise a surprising insight came to us. It seemed so counter-intuitive at first, then as we kept exploring it became so blindingly obvious that we questioned our intelligence for not thinking of it before. What was this revelation, you ask – and more importantly, why should you care? An Architect doesn’t need a Blueprint. Let’s step outsi... (more)

A Recipe for Cloud Design

The deployment of infrastructure systems to support applications has been a challenge since we first developed a choice beyond the venerable mainframe. To some it’s a simple formula; take a server, toss in a little network and storage, bake for a few weeks and you’re done. If you’re having a few friends over (need a little more) then simply add a few more servers and you’re done. What the heck, hardware is cheap and gets cheaper every year...the advent of Cloud makes it even easier to maintain that philosophy. Unfortunately that mentality is pervasive in much of IT, not to mention ... (more)

Business Value and Cloud Computing

In our last post we discussed the positive shift in the Cloud Computing discourse towards actionable steps rather than philosophical diatribes on definitions. And to support that discussion we offered the following list of things not to do: Not understanding the business value Assuming server virtualization is enough Not understanding service dependencies Leveraging traditional monitoring Not understanding internal/external costs In this installment we are going to focus on the first mistake - failing to understand the business impact of leveraging a Cloud delivery model for a g... (more)