This is a single archived entry from Stefan Tilkov’s blog. For more up-to-date content, check out my author page at INNOQ, which has more information about me and also contains a list of published talks, podcasts, and articles. Or you can check out the full archive.

Service Component Architecture

Stefan Tilkov,

IBM, Oracle, BEA, SAP, IONA and others have published version 0.9 of SCA — the Service Component Architecture. I’ve just taken a quick look at the whitepaper, and I have to admit I’m severely underwhelmed.

Just as an example, take a look at this paragraph:

SCA will support REST style Web services by supporting a REST Web services binding. SCA components can implement REST style Web services by means of offering their services using the REST binding. Similarly, SCA components can invoke REST style Web services through the REST binding. Other than a change of binding, using REST Web services is similar to the use of Web services using SOAP and WSDL bindings.

Wow, take a look at that — REST is just an implementation detail. That’s great! I have a great idea — why don’t we just invent a JAX-RPC-to-REST-adapter? Excuse me while I’m gone, I’m busy getting rich.

On December 1, 2005 2:09 AM, Oliver Wolf said:

After skimming over the whitepaper and browsing the more detailed specs on IBM’s website I’m still wondering what all this is about. Is SCA a novel view on SOA or is it just JBI for the rest of us? If the latter is true I’m a bit confused to see three of JBI’s main proponents — Oracle, SAP and IONA — get involved with SCA.