"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.

« Service Analysis: Defining effective Service Oriented Architecture | Main | Yet another attempt to define services! »

SOA, BPM, Components, Objects proponent's views

Today I was reading a blog on zdnet about how SOA can be used and is being used in a non-IT world.

http://blogs.zdnet.com/service-oriented/?p=795

I have posted my repsonse on this blog as follows:

SOA proponents view the world as SOA fabric. BPM proponents tend to look at everything in terms of processes. The proponents of Compnents based design / OO tend to view the world made up of distinct objects / components. All of these views have its merits. We need to leverage SOA to see everything(discrete services) linked together through well defined interfaces and as JP pointed out remove the tight coupling between the service provider and consumer. Each of the services are made up of 1 or more business processes. The services are attached to objects or components. Once we get a clear picture of the merits of each of these school of thoughts it becoms easier to address a problem and provide an effective solution, be it a IT or non-IT scenario.

TrackBack

TrackBack URL for this entry:
http://www.infosysblogs.com/soa-mt/mt-tb.fcgi/32

Comments

Well, I kind of subcribe to JP's thought, that SoA is essentially a design pattern. And truly it is. The way I see it is as whether it be Services or components or anything else, all ultimately expose and implement a business process. The pro's and cons of each approach only matters during implementation.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)