Ready for the SOA Journey: Check Your SOA Maturity
- Do you have enough buy-in from Business, IT and other key stakeholders and of course the right business case to adopt SOA?
Continue reading " Ready for the SOA Journey: Check Your SOA Maturity" »
Continue reading " Ready for the SOA Journey: Check Your SOA Maturity" »
Continue reading "SOA Reference Model & Reference Architecture – The Link" »
The SCA Java EE Integration Specification has been released. It is quite an interesting read. The vision of SCA is to build composites and composite applications out of configurable, reusable service components or assets as I had tried to explain earlier. It does not intend to replace existing open standards but to build over those standards to enable a technology agnostic service component integration platform. So it has support for multiple communication protocols (or binding types), component implementation languages (implementation types) and component interface languages (interface types). The list of these types is growing. Also I had mentioned (SCDL vs WSDL) the promise to support so many technologies in a standard manner is indeed a big one! This often gives rise to skepticism in some quarters and comparison with similar looking standards such as the JBI.
Continue reading "SCA Java EE Integration Spec brings the Java world closer to SCA" »
What is that SCA does which WSDL couldn’t already do! ?
Well, on the face of it, it may look quite an answerable question but its implications go deeper on second thoughts and perhaps makes one think deeper about the future of SCA and perhaps make educated guesses about it. Here, I will try to answer this question and one need not know anything about SCA (except that it is a superseding component specification model which promises the heaven – no plumbing code only business logic, remember!). I will assume you have fair understanding of WSDL. SCA promises to be an interesting component specification on the horizon and backed by big names such as IBM, SAP, etc. so no harm spending some time understanding it. Seems like it is logical evolution from the J2EE component specification and some basic ADL concepts – component, interface and connectors…In fact most of the concepts are familiar in the Java world (references, annotations, etc.).
'SOA has created unexpected complexity' what caught my attention and reading through the article I hit upon another unexpected term -
‘The Ovum survey found a high correlation between a business' level of satisfaction with SOA and their commitment to managing IT as a set of services.’
Surprised! services being tagged with IT, services being abstracted to such a large extent (as my thoughts were channelized only on to SOA)... I continued reading and among examples was what I found - ITIL. So it was about ITIL, a framework and set of best practices to be followed for IT management and operations.
The intended grand vision of a universal service broker though has fallen down; the need for cataloging service is however being more and more realized as critical pieces in solving the puzzle of realizing SOA. Till early last year there had been various products offering service-cataloging features based on UDDI standards. But now we see another terminology being thrown across called repository.
Continue reading "Yet another attempt to define services!" »
While SOA has been advocated as the automation mantra for application to application interaction (including integration, collaboration), Web 2.0 is being promoted as the new trend in rich client computing with rich computation power on the front end platforms.
Is there a relation between Web 2.0 and SOA? We explore in this track of research
Read on.
Yet another research dimension of SOA.
While SOA abstracts IT functionality on basis of standards, these standards base themselves on XML as the core representation format. The dependence upon XML imposes performance constraints due its verbosity, and need for parsing.
How can we do research to overcome the performance challenge of XML in SOA? Read on..
In continuation of past post on research directions in SOA, one key issue that often bogs the enterprise integration architects is the balance between realistic integration solutions and hyped approaches like the next IT wave.
In that context, events are a natural language for EAI practitioners to understand. Read on..
Quite often IT waves which trigger a huge hype initially, followed by a more realistic expectation setting among practitioners, the real gaps needing deeper research and insights, come to the fore.
At this moment, SOA is slowly moving from hype to reality. In this transition, apppear like a pandora's box the enormous challenges which can aid practitioners adopt SOA realistically and practically.
At Infosys SETLabs, we are constantly working on research directions to help practitioners adopt SOA with a realistic and practical approach.
To list these areas:
Recent trends in EAI practices indicate the coming of mainstream of event driven architectures.
However, the complementary trend of SOA is still to recognize the value of events and event driven architectures for generating scaleable SOAs. Event driven SOAs are occupying the mindshare of a lot of SOA practitioners, and vendors like TIBCO etc.
However the catalyst to coming of event driven SOA might be in form of standards?
Continue reading "Are standards the answer to Event driven SOA?" »
SOA is not just about software architecture or technology
A recent survey by Ovum of 333 U.S. IT decision makers has formally announced what was obvious all this while. One in five surveyed have said that moving to SOA has created unexpected complexities.
To me, the root cause seems not to be with SOA itself but with not expecting the complexities that come with its uncontrolled adoption. There are hundreds of definitions for SOA, the tricky part is that each one of these is correct in its own context. For example, product companies are promoting a more product centric definition of SOA, which will help them sell their products. However, most of these definitions miss out on the big picture. Its like "six blind men and the elephant". What is essentially missed out is that SOA is not a technology but a concept, that its an enterprise software architectural style, its a "disruptive" way of organizing and managing business with support from agile software services.
Continue reading "Hype seems to be over, reality sinking in...!!" »