Comments on: Capitalizing on your Legacy in SOA

By: Rob Morris

Rob Morris — Fri, 16 Feb 2007 14:57:35 +0000

Amen! There are certainly plenty of folks who do equate web services with mainframe SOA (a lot of this thanks to the good people at IBM);->

We work very hard to dispel that myth, and try to get people to focus on the social issue of getting people across mainframe and distributed envrionements to work together on the defintion of right-sized services.

Then you need the ability to utilize a contract-first design pattern so that you can map pieces of existing functionality to the service you require (as opposed to taking what you have and creating a million little services that require further composition to be meaningful within your SOA).

This is the world I live in every day, so I’m always happy to discuss further.

By: Tobias Strandh

Tobias Strandh — Sat, 10 Feb 2007 14:22:50 +0000

Really interesting reading here. I agree with Anders that you’re defenitely on to something here. Will come back to read more!

By: Anders Tornblad

Anders Tornblad — Fri, 09 Feb 2007 20:27:07 +0000

You are, as always, spot on! In my eyes, this is a special case of SOA anti-pattern “Equating SOA with Web Services”, where covering just about anything in scented, bubbly SOAP is considered enough to label any architecture (or lack thereof) SOA.

Any technical decision, like wrapping something in Web Services, that is not a result of business level and conceptual level analysis, should make all warning bells go off. At least when you claim to do SOA…