I was at IBM’s annual analyst conference last week and the excitement levels among staff about Service Component Architecture was palpable.
Its such a weird industry – we get excited about the introduction of a new abstraction layer…
SCA is a specification designed to augment Service Data Objects (SDO).
IBM claims it underpins SOA as a programming model. Good luck with that.
I wondered at the time if IBM was so jazzed because it thinks it sees SCA as a potential chink in SAP’s armour? Wishful chinking, perhaps? Is it really likely this consortium is going to get things done: BEA, IBM, IONA, Oracle, SAP, Siebel Systems, and Sybase? Or are we just trying to hide the turd?
I am sure Oracle and SAP can’t wait to provide competitors with an end run around the data closely held in their business applications.
I am skeptical SCA will deliver the benefits claimed, any time soon. Today I see that the WD at MWD has written the piece I would have, but with better J2EE backgrounding. So rather than repeat another analyst I simply concur: what he said.
Seems like Dana is pretty negative too.
My own linguistic bugbear- is it a service or a component? A wave or a particle? For composite apps or component business models. Doh!
It is certainly worth noting (reporter alert!) that Jim Marino at BEA says we will see an open source runtime for SCA. Bring it on. But then he also says the spec is far from complete.
So what else is new…