SOA / Web Services / Java

A Technology Blog

Archive for August, 2008

SOA Governance

Posted by Vivek on August 23, 2008

Any organization willing to implement SOA should already have a plan for its governance. Most people think that SOA Governance is optional and it’s not true. Without SOA Governance it is impossible to reap the true benefits of a full-fledged SOA. Some benefits that are directly related to success of any organization.

With the widespread adoption of SOA, the challenges associated with SOA projects are emerging. SOA governance isnt optional its imperative. Without it, return on investment will be low and every SOA project out of pilot phase will be at risk.
                                                        Paolo Malinverno
                                                           Gartner, Inc.1

Failure to provide effective SOA governance exposes your organization to serious risks:
• Insufficient knowledge of available services
• General failure to reuse services
• Unnecessary, uncontrolled service duplication
• Resources wasted on services that can’t be reused
• Service sprawl across siloed SOAs
• Ineffective communication of best practices.


A good blog on SOA Governance:

Posted in SOA Governance | Tagged: , | Leave a Comment »

Defining SOA

Posted by Vivek on August 23, 2008

If you ask 5 different people definition of the buzzword “SOA”, they all will come with a different answers. SOA is not something that can be defined in two or three lines. 

“SOA is the architectural style that supports loosely coupled services to enable business flexibility in an interoperable, technology-agnostic manner. SOA consists of a composite set of business-aligned services that support a flexible and dynamically re-configurable end-to-end business processes realization using interface-based service descriptions.”

To be more precise, any SOA must exhibit the following features:

Loose coupling – Services maintain a relationship that minimizes dependencies and only requires that they retain an awareness of each other.

Service contract – Services adhere to a communications agreement, as defined collectively by one or more service descriptions and related documents.

Autonomy – Services have control over the logic they encapsulate.

Abstraction – Beyond what is described in the service contract, services hide logic from the outside world.

Reusability – Logic is divided into services with the intention of promoting reuse.

Composability – Collections of services can be coordinated and assembled to form composite services.

Statelessness – Services minimize retaining information specific to an activity.

Discoverability – Services are designed to be outwardly descriptive so that they can be found and assessed via available discovery mechanisms.

This is important when the following objectives are to be achieved:

• Reducing overall total cost of ownership (TCO)
• Improving time to market
• Achieving business agility
• Fostering innovation
• Enabling compliance
• Improving the top and / or bottom line
• Increasing customer satisfaction and retention
• Global expansion

Posted in SOA | Tagged: , | Leave a Comment »

SOA Best Practices

Posted by Vivek on August 9, 2008

Hundreds of Organizations are trying to demystify SOA and each wants to win the race by providing the best possible solution even if the infrastructure becomes heavy in the process.

Here is a good link which clears the air to a large extent:

Oracle’s breed of products in making SOA a reality are unmatchable:

Posted in SOA | Tagged: , , | Leave a Comment »