"We didn't start the fire ... it was always burning since the world's been turning ..." [Billy Joel 1989]. Is SOA the "Same Old Architecture?" or is it "Simply Over Ambitious?" Let's apply SOA's arsenal:: XML, BPM, Services, SOAP, Web Services - to the real world and find out. Let's put out some fires.

« October 2006 | Main | December 2006 »

November 17, 2006

Who pays the bill for enterprise SOA initiatives?

Your company is in Fortune 500 or 5000; an Oil & Gas major with north of 200 billion in revenue or privately owned ‘niche’ with south of a billion in revenue, it does not matter. The question is the same: who will fund the SOA initiatives in the enterprise? 
 

The answer is simple: everybody and nobody.


As Steven Johnson articulates in his book, Emergence: The Connected Lives of Ants, Brains, Cities, and Software, often the SOA investments are never from a single source. Inline with the core principles of SOA  i.e. the distributed nature of enterprise systems, the investments comes from varying sources. Johnson’s basic theory goes likes this. “An individual ant, like an individual neuron, is just about as dumb as can be. Connect enough of them together properly, though, and you get spontaneous intelligence. (source: amazon.com)”.


In an organization, the individual business computations wrapped in services are like ants. In isolation, the services may be less intelligent and less agile. The ability to create different formations from services in a flexible manner provides the agility that organizations often aspire for. Often the funding to create this formation comes from more than one source.

Often, organizations spends IT dollars in
1) Sustenance of the existing application and infrastructure
2) Revitalizing existing platforms (e.g. platform migration) and
3) Developing new systems and platforms based on business initiatives.
 

Each of the above sources of money can become donors to SOA initiatives. The following three examples provides their contribution to Enterprise SOA
1) Through sustenance dollars, the information on legacy applications portfolios can be created, which can be become the cornerstone of legacy service harvesting initiatives.
2) While platform revitalizing efforts are taking place, organizations can make sure that the new platforms support SOA capabilities.
3) Business services can be realized through new development activities.
 

To make this enterprise service ecosystem work, organization would need a SOA vision, future state blueprint, execution roadmap and governance model that can tie the different initiatives in the organization together. This upfront, but loosely coupled, planning provides the rich environment that encourages the service orientation and makes the emergence of a ‘connected’ enterprise.  

November 06, 2006

Effectiveness of SOA - Dressing the edifice of enterprise with new paint

Most of the work on SOA that are seen in many of the online (Link 1, Link 2) or print media would either refer or talk elaborately about the governance.  With every one singing in the same tune it is obvious hint that success of a SOA in an enterprise is directly linked to governance.  As many would suggest... (Read on further)

As many would suggest it’s a good idea to quickly form a team that directs, controls and decides, but with enterprises having very rigid hierarchies it’s a colossal task.  With thoughts to bring various business units (some of them could even be geographically apart) just exacerbates the possibility. Analogous to above statements, there have been interesting comparisons made towards building kitchen and undertaking a SOA program <Link>. But having lived in the house for decades or in some case centuries most of them would not like the idea to bring down or reorganizing. So to make-over we would have to look at various means to effectively dress the edifice with a new paint (may be with least possible rework).  

Various approaches/methods have been discussed on governance like Demand-Supply or approach from others (IBM).  Of all these an important aspect of governance that stands out is communication. It forms the basis of all effective governance.  It’s important as much as getting the right shades of the paint. Plain shades would not induce much interest and heavy shades will only wary people. The need for getting communication among people right is because of follwoing reasons -

  • Involvement of cross functional people with in enterprise
  • Involvement of multiple vendors
  • Activities being apportioned however under common context
To get the communication for an SOA program right we have to understand various roles (possibly some new), define who does what, when and in which capacity.  Then align the new decision rights and accountabilities with the existing organization structure. This would encourage desirable behavior in the use and achieve efficient and effective team work.