Archive for the ‘Architecture’ Category

Importance of SOA Governance

July 9, 2007

I was reading a Gartner press release on SOA risks. This report highlights some technical and organizational factors that can lead to SOA failure.

“Right level” of governance, and “right level” of service granularity is required for SOA success according to the press release. This again highlights the importance of A in SOA – you need architects to identify the “right levels” and the architect should architect the system with “right levels”.

In other words, the enterprise architecture with service-oriented characteristics is unique to each and every organization.

Among other risk factors, are the documentation and bad selection of components. These are simple factors that we always know that should be in place, but always overlooked. When selecting components, often politics and marketing hype play a bigger role than technical feasibility.

A in SOA

July 7, 2007

There are many who raise concerns on SOA being driven out of its true meaning, mainly because of the hype related marketing surrounding it. However, I have seen some real SOA experts raise concerns on missing A in SOA.

Many people, even software architects, fail to look at SOA as an architectural pattern. Some software vendors try to market products with SOA, and people tend to think that you can place that product in the enterprise IT stack and archive SOA. This school of thought is really against the principles of SOA. Each and every organization need to look into their enterprise needs and build the service oriented architecture. Vendors can have products that assist to realize SOA.

It is incorrect to focus on the technology, when trying to come up with an SOA that suites an organization. Unfortunately, even today, many architects tend to do so.