David Chappell has just posted a good primer explaining exactly what Service Component Architecture (SCA) is and why we should care about it.In the paper, David explores the properties of components, SCA's Java Component Model, composites, policies, and implementing SCA.
Latest from Joe McKendrick
The software business is going, going gone. What's going to take its place?
UDDI is finally starting to see its day in the sun -- what was the holdup?
SOA is actually SaaS, delivered internally -- and ultimately, externally.
With SOA, Web services, and SaaS, we can all be both publishers and consumers of services. That's the beauty of it all.
Okay, time to mix it up more with the SOA-Software as a Service connection. I just got word that StrikeIron reports it had a very good first quarter, adding over 175 new customers in the first three months of 2007, with revenue increasing six-fold over the same period in 2006.
Radovan Jacenek saw my post and others on the SOA-SaaS connection, and puts the relationship in the most concise, to-the-point context I've seen so far:"I'm kind of surprised there even is such discussion because it seems so obvious to me: you need to implement SOA in order to deliver good SaaS." 'nuff said.
Service as in SaaS has a different meaning that service as in SOA.
An industry standard is a great idea -- every vendor should have one of its own. The industry has made some progress in getting vendors to line up behind standards, but vendors being vendors, they still always insist on releasing their own flavor of standards in products.
Software AG and WebMethods have a lot of overlapping technology. Why buy?