Keystones and Rivets

Understanding SOA

Over the past year or so there has been a huge increase in the amount of discussion about Service Oriented Architecture (SOA), and the number of blogs and posts on the subject seems to increase daily.

So with over 25 million references to SOA discovered by Google, why bother writing another SOA blog post?

Much of the discussion amongst the SOA community is interesting to other technophiles, but only serves to confuse the majority of readers.  Bloggers like Mike Kavis try to bring the focus of SOA back to a business perspective, but the vast majority of articles concentrate on the technology debate.

In recent weeks the rise of a lightweight version of SOA, termed Web Oriented Architecture (WOA), has had the techno-bloggers tapping away at their keyboards.  OnStrategies gives us a quick digest of some of the highlights.

Rather than join the technology debate about SOA we’ll take a step back and explain simply how it works, how it can be used and, with the use of a real-world example, describe why a properly planned and implemented Service Oriented Architecture can create a flexible way of aligning business and IT.

Cloud Computing

LUNKWILL:  Are you not as we designed you to be, the greatest, most powerful computer in all creation?
DEEP THOUGHT:  I described myself as the second greatest …Deep Thought… and such…
LUNKWILL:  Yes yes but…
DEEP THOUGHT:  …I am.
LUNKWILL:  But, but, but - this is preposterous! Are you not a greater computer than The Milliard Gargantu-Brain at Maximegalon, which can count all the atoms in a star in a millisecond?
DEEP THOUGHT:  The Milliard Gargantu-Brain, a mere abacus. Mention it not.
FOOK:  And are you not a more fiendish disputant than The Great Hyperlobic Omnicognate Neutron-Wrangler? Which can destroy -
DEEP THOUGHT:  The Great Hyperlobic Omnicognate Neutron-Wrangler can talk all four legs off an Arcturan Mega-Donkey but only I can persuade it to go for a walk afterwards. Molest me not, with this, pocket calculator stuff!
LUNKWILL:  Then what's the problem?
DEEP THOUGHT:  I speak of none, but the computer that is to come after me.

(The Hitchhiker's Guide to the Galaxy)

Nick Carr recently commented on IBM's new initiative called Project KittyHawk, which sets out to use their Blue Gene technology.  The project aspires to create a “global-scale shared computer capable of hosting the entire Internet as an application”.

There have been a range of online discussions on the back of the article as, once again, Nick Carr manages to hit more than a couple of raw nerves.

The premise of the article is that IBM Blue Gene technology is creating computers of such power that data centres can offer vast amounts of  computational power that businesses can plug into and use according to need at a particular time.

These supercomputers can emulate many individual smaller servers (virtualisation) so businesses can migrate their IT services to this new model.

Rather than data centres just offering a place to put your own servers, they can start to offer virtual servers or services, enabling new business models to be adopted.

The IBM technology is so fast that Project Kittyhawk can emulate the entire internet. 

Understanding Enterprise Architecture complexity

Nick Malik of Microsoft posted recently that

“For years, we've been living with Zachman and now TOGAF as commercially available EA frameworks, but honestly, they don't address the problems faced by large organizations with respect to complexity.”

This got me thinking about some of the pros, cons and limitations of the traditional frameworks used in Enterprise Architecture (EA).

This isn’t a comprehensive review but I’m going to briefly discuss three frameworks and their limitations in this blog, before I talk a little about OBASHI™ - my company’s own framework for capturing Business and IT related information.  Each framework details how information can be categorised, organised and presented to form the basis for governance and change.  The three traditional frameworks have some key differences which I’ll highlight below. 

Archaeological Digs & IT Relics

Investigating the systems architecture and infrastructure of any reasonably established complex organisation is as revealing as an archaeological dig in turning up the relics of its evolution.

There will usually be a basic proliferation of hardware and software platforms with department or task specific functionality; overlapping or parallel systems; and instances of multiple input of data, with all the potential that has for conflicting information. Superimposed upon this may be more sophisticated systems based on database technologies which have resulted from or facilitated the re-engineering of its business processes.