No hanging chads here, we promise! Login and vote now.
By cp29422
via manageability.org
Published: Jun 12 2008 / 07:25
There's this ongoing argument in the blogosphere on the issue of the "importance of Cohesion in SOA". Cohesion and Coupling are two features that should be present in good software. The paradox is that they're opposite forces and a balance between them has to be made. The ongoing argument is that SOA tends to lean towards loose coupling and therefore cohesion must be compromised. What both surprises me and keeps me equally disgusted is the fact that SOA practitioners can't even get a handle on this simple concept.
Comments
Dhananjay Nene replied ago:
Strange .. will not allow me to post a comment without creating a userid on the site. Posting comment here.
Its a designers job to manage both coupling and cohesion. If he is unable to get a decent balance, either he's been given a completely impossible set of technical requirements, or time for him to explore other opportunities.
All the good old principles continue to be true with SOA (or any other distributed computing paradigm). The additional issues that need to be considered are : Granularity (can't run fine grained calls over the network), Latency (introduced by the network) and Multiple Points of Failure.
Voters For This Link (8)
Voters Against This Link (1)