Point-counterpoint: Is SCA the limit?

There's been a blogstorm swirling around Service Component Architecture (SCA), and Loraine Lawson has done a great job of summing up both sides of the discussion.

To sum up, there are two points of view on the efficacy of SCA:

Anti-SCA: "SCA is heavily being driven by the vendor community and SCA breaks many of the rules of SOA that have been touted by these same vendors for the past six years.... SCA is a step backwards in software engineering.  It’s an abandonment of the SOA principles that have failed because of lack of investment in proper architecture toward a pure programming model driven by software engineers.  Thus, the goal here is once again to allow poorly-designed systems to be built by software engineers with very little architecture experience so they can claim to have some attributes of SOA." -JP Morgenthal

Pro-SCA: "SCA is a key new technology that will help people achieve... greater simplicity, better service design, higher productivity and less dependence on large software stacks. I hope anyone... interested in these goals takes the time to take a closer look at the technology." - Michael Crowley, author of Understanding SCA: Revolutionize How You Build BPM Applications.

Loraine observes that organizations need to concentrate on business requirements, not tools -- and nurturing the skills that can help meet those needs.