Archive for January, 2010

muSOAing for 1/31/10

January 31, 2010

Coming back to our SOA for world peace initiative. The last we left it was at designing the canonical. I was mentioning that the canonical should be managed through a SOA Competency Center overseen by a benevolent dictator. Now let us talk about the composition of this Canonical. How should it be structured, what elements should it contain.

I would imagine that this schema would form part of a SOAP payload during transmission and should essentially contain at least these two sections. A Header and a Body, this should not be confused with the SOAP header and body sections which are separate. The header section will contain important key attributes, sort of metadata about the payload itself.

One important thing to remember is, since we are talking about world peace, all information originating is such a payload should pertain to those aspects of peace that either serve to promote and further peace or are a threat to peace in any part of the world. So with this in mind, let us try to identify a few attributes.

Since threats are normally directed at or affect nations, one very important attribute will be Nation Code. So the header will contain at least these codes,

1. Nation Code (Nation against which Perception is directed)
2. Origination Nation Code (Nation that identified or detected perception)
3. Perception Code (Peace or Threat)
4. Perception Level (Threat Level)
5. Description (Nature of Threat with detailed description)
6. Security Agency (FBI, Interpol, MI6, RAW, FSB or agency that identified perception)

In the next post we will examine the composition of the Body and any remaining elements that need to be added to the header.

In subsequent posts we will try to come up with some valid use cases for the contents of this payload and for the manner in which such messages will be exchanges which can be either in a peer to peer fashion and/or a hub and spoke fashion.


muSOAing for 1/21/10

January 22, 2010

While SOA has become pervasive and very mainstream, it is quite interesting to note how it has enabled newer paradigms like SaaS and Cloud. While SaaS has become a popular way for CIOs to hive off entire non-core and industry standard business processes and functions to be executed on SaaS platforms. This has turned out to be an extension of their IT arms.

The beauty of SaaS is, an employee in Tokyo can fill out his timesheet using a system hosted in Timbuktu. This same system could be serving employees in Tashkent or Texarkana. Here is a case of an application being served over the web with co-location to serve multiple clients desiring the same functionality. The same functionality can be executed as an API as a discrete function or step in your business process and this where SOA plays an important role.

Then came Cloud Computing. Cloud, bits, bytes, mapreduce, hadoop. An entire new industry spawned by an algorithm. Is that an oversimplification?

muSOAing for 1/14/10

January 14, 2010

Our SOA for peace project is still on. A few topics have been crying for attention lately and chief among them is Cloud computing. This is a very interesting area and is only going to gain momentum and grab a lot of headlines in the coming weeks and months.

It is very hard to describe what a Cloud is from a consumer perspective but believe me it is out there are it is a part of our everyday life. From a provider’s perspective, a Cloud is several things and most of all it is the erasing of these boundaries between Software, Application, Server and Storage. It is a Virtualized world on steroids. There will come a time when you do not think of these as their individual physical instances but rather as spare computing units that are available for use. So you are optimizing server utilization by pooling their resources through virtualization.

With increasing adoption, the day is not far when this technology will be commodotized with even opensource offerings. Though it is currently the preserve of only the biggies, every IT organization however small is also realizing the benefits of this technology and a lot of vendors are busy building Cloud Computing solutions.

muSOAing for 1/6/10

January 6, 2010

My first post for the new year. Let me start by wishing everyone a belated Happy New Year. Let this decade be the one for total SOA Adoption. This is the decade that everyone will adopt the Color TV of Integration Technology.

One question that keeps cropping over and over again is this comparison between EAI/MoM technologies and Middleware. People tend to speak of them in the same breath as if they were peer and competing technologies. Well they are not. Think of EAI as Integration 1.0 and SOA as Integration 2.0. SOA does mitigate a lot of the issues that one faced with EAI.

EAI and MoM were never perceived as enterprise caliber contenders. SOA came in, improved upon all their deficiencies and became the truly Enterprise level Integration Paradigm and Technology. EAI was confined mainly to the Business Unit or Department and could never really make that leap to the Enterprise.