Understanding SCA (Service Component Architecture)

Understanding SCA (Service Component Architecture)

by Jim Marino, Michael Rowley
4.7 10

NOOK Book(eBook)

$23.49 $39.99 Save 41% Current price is $23.49, Original price is $39.99. You Save 41%.
View All Available Formats & Editions
Available on Compatible NOOK Devices and the free NOOK Apps.
Want a NOOK ? Explore Now

Customer Reviews

Most Helpful Customer Reviews

See All Customer Reviews

Understanding SCA (Service Component Architecture) 4.7 out of 5 based on 0 ratings. 6 reviews.
Anonymous More than 1 year ago
DO MEEEE!!!! Mrnoob467
Anonymous More than 1 year ago
Moonstar here im at res 5 and how do I do those symbols? Lol thx
Anonymous More than 1 year ago
Do me signed RFace360
Anonymous More than 1 year ago
Could you do my name please? Signed skydoesminecraft
Anonymous More than 1 year ago
Just put your name at res 1 and look for your name at other results. And if you dont like it ask for a redo at result 1.
Boudville More than 1 year ago
The basic aim of the book is well described in its first chapter. It tries to define a standard for writing distributed systems that is analogous to object oriented ideas for writing a single system. SCA builds on its predecessors; notably CORBA and DCOM from the 90s, and Java EE and .NET from the noughties. At this point, if you are a EE or .NET person, you probably agree that CORBA and DCOM were flawed. But you would probably disagree about EE or .NET itself. The book argues that those two, while better than the 90s, also have taken on increasing complexity. A multitude of standards like JDBC, JPA, JMS and EJB have flowed in the java world. While the .NET environment also have equivalents to address similar needs. Interestingly as a point of sociology, SCA also is deliberately different from how CORBA and EE arose. Those were complex standards put together by official committees. SCA was designed to change quicker, by being at its core somewhat ad hoc industry collaborations. If you are a java programmer, the flavour of the book's technical discussion is like an extended foray into the use of java interfaces. Just an analogy. But the explanation of making components that can then be used in services makes this a good one for understanding. Also, on pages 72-3 is a very succinct explanation of why EJBs never really took off, due to the performance penalties for remote calls and the complexity of the EJB code. If only the EJB books from 10 years ago had told us!