Udooz.net

SOA - The three letter acronym is survived and appeared as a promising approach in the enterprise SOA, thanks to the technologies whomsoever it makes SOA more mature.  When I was started learning SOA from its infant state to the current.  People who are involved in SOA implementation and adoption might know that there are more things to be considered apart from the four tenants of SOA, and the technologies WCF, Webspheare, Java WSDP/J2EE, etc.

In this series, I'll share my learnings on SOA adoption in the enterprise space.  Some of my learning could be a pattern, some would be preferrably pattern and of course some are not.  I had spent lot days on where to start and how to start.

What is the difference?

There are so many SOA books in the market, each books cover the topic from different perspective.  However, to confirm the theory, I've learnt more than five books.  Enough.  These SOA books are excellent in theory and covered the practical scenario much higher level.  The ground level decision making is up to the technology you have used, then YOU.  Yes, you.

My objective on this series of article is very clear.  There are some ground level patterns required to really implement and adopt SOA.  The fundamental SOA theories and technologies will help up to some extent.  I am covering the another extent.  And, If you want to really learn the theory and other terminology definitions, please read some good SOA books.

Objective of this series

• Practical solutions for some practical problems during SOA implementation.
• Not much theoretical

Let us start

Let us start with the definition for service.  A software system which provides a particular business functionalities which can be accessible from any other system over network by means of mutual understanding between these systems.  CORBA, DCOM and now web services are various avatars of services, fortunately web services are the only practical methodology now for SOA which merely adhering the four tenants of SOA.

The Four Tenants

1. Boundaries are explicit.  Service contract clearly conveys what are the capabilities available from a service and its input and output details.
2. Services are autonomus.  Services and its consumers should be independant.
3. Share schema, not the implementation.
4. Compatibility based on policy. All the pre-requisitie for the service should be mentioned as part of its contract.

 Microsoft Windows Communication Foundation hopefully setting the stage to compete these tenants with its highly extensible architecture.  An introductory MSDN tutorial about WCF lets you aware this. The good starting point related to this title would not be the fundamental SOA guidelines and WCF tutorial.  From a case by case manner of an enterprise perspective.

< Prev