Understanding SCA (Service Component Architecture)

Overview

Use SCA to Simplify the Development and Delivery of Service-Based Applications

Service Component Architecture (SCA) is a new programming model that enables developers to build distributed applications more efficiently and effectively than previous technologies. In Understanding SCA (Service Component Architecture), two leading experts offer the first complete and independent guide to SCA. Drawing on extensive experience both developing the SCA standards and implementing ...

See more details below
Paperback
$34.84
BN.com price
(Save 30%)$49.99 List Price
Other sellers (Paperback)
  • All (17) from $14.82   
  • New (10) from $19.89   
  • Used (7) from $14.82   
Understanding SCA (Service Component Architecture)

Available on NOOK devices and apps  
  • Nook Devices
  • NOOK HD/HD+ Tablet
  • NOOK
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac
  • NOOK Study

Want a NOOK? Explore Now

NOOK Book (eBook)
$22.79
BN.com price
(Save 43%)$39.99 List Price

Overview

Use SCA to Simplify the Development and Delivery of Service-Based Applications

Service Component Architecture (SCA) is a new programming model that enables developers to build distributed applications more efficiently and effectively than previous technologies. In Understanding SCA (Service Component Architecture), two leading experts offer the first complete and independent guide to SCA. Drawing on extensive experience both developing the SCA standards and implementing large-scale SCA applications, Jim Marino and Michael Rowley provide an insider's perspective for developers and technical managers tasked with architecting and implementing enterprise systems. Rather than simply providing a technology overview, the authors draw on their practical experiences with SCA, explaining

  • The full history behind SCA
  • How SCA fits with other enterprise technologies such as JEE, .NET, Web Services, and BPEL
  • All the major SCA concepts including composition, policy, wires, and bindings
  • Best practices for designing SCA applications
  • Using SCA with Web Services, Message-Oriented Middleware, BPEL, JPA, and Servlets

Understanding SCA (Service Component Architecture) provides the background necessary to make informed decisions about when and how to best use SCA to build enterprise applications.

Read More Show Less

Product Details

Meet the Author

Jim Marino, Ph.D., is Principal at Metaform Systems, where he provides strategic planning, architecture assistance, and training to clients worldwide. Jim is also one of the architects of the Fabric3 SCA runtime. Prior to joining Metaform Systems, Jim was Director of Technology at BEA Systems, where he was involved with the development of Service Component Architecture from its inception.

Michael Rowley, Ph.D., is the CTO of Active Endpoints, Inc. He has been involved in the development of SCA from early in its development and has contributed to 12 of the 15 SCA specifications that were published as part of the Open Service- Oriented Architecture (OSOA) collaboration. He was also an original member of the Open Component Service Architecture (OpenCSA) steering committee, which is the OASIS steering committee that oversees the work of the various SCA technical committees. Before joining Active Endpoints, he was a Director of Technology at BEA Systems where, in addition to working on SCA, he also helped develop the BPELJ extension to BPEL and was involved in the early development of BEA’s event processing and service bus products. Michael received his Ph.D. in computer science from UCLA in 1994.

Read More Show Less

Table of Contents

Preface xix

Chapter 1: Introducing SCA 1

Chapter 2: Assembling and Deploying a Composite 41

Chapter 3: Service-Based Development Using Java 69

Chapter 4: Conversational Interactions Using Java 109

Chapter 5: Composition 131

Chapter 6: Policy 167

Chapter 7: Wires 189

Chapter 8: Bindings 203

Chapter 9: The Domain 231

Chapter 10: Service-Based Development Using BPEL 267

Chapter 11: Persistence 285

Chapter 12: The Presentation Tier 311

Index 325

Read More Show Less

Preface

Preface

What is Service Component Architecture (SCA)? What are the key SCA concepts? How will SCA impact technology choices my organization will need to make in the near-term? How should SCA fit into my enterprise architecture? How can I make the best use of SCA in my projects?

Answering these questions is fundamental to understanding SCA. The goal of this book is to help answer those questions by providing the background necessary to use SCA effectively.

Who Can Benefit From This Book

SCA is a technology for creating, assembling, and managing distributed applications. However, this book is not intended solely for developers. Our aim is to benefit "technologists"—developers, but also architects, analysts, managers, and anyone who has a stake implementing information systems—by connecting SCA to broader technology trends.

In this book, we attempt to strike a balance between the "big picture" and the detailed coverage essential to developers. We also endeavor to achieve this balance in a way that is engaging, accurate, and complete.

Both of us have been involved with SCA since its inception, when it started as an informal working group composed of individuals from IBM and BEA (where both of us worked). We have been directly involved in shaping SCA as it went through various iterations and changes. Rather than simply provide a tutorial, we have sought to explain the history and reasoning behind important decisions made during the development of SCA.

Lest we be accused of operating in the "ivory tower" of technology standards, we have also attempted to be informed by practical experience. We have been key contributors to the opensource Fabric3 SCA runtime. In addition, while at BEA and now in our current positions, we have had the opportunity to be involved in the development of several large-scale systems built with SCA. We have tried to reflect this experience and lessons learned throughout the book in the form of best practices and implementation advice.

Finally, while we strive for completeness and accuracy, there are inevitably things a book must leave out. SCA is a vast technology that spans multiple programming languages. We have chosen to concentrate on those aspects of SCA that pertain to creating and assembling applications using Java. Although we touch on BPEL, our focus remains on Java, as the latter is a cornerstone of modern enterprise development.

How to Read the Book

Reading a book is like listening to an album (or CD): Both are highly personal experiences. Some prefer to read thoroughly or listen from beginning to end. Others like to skip around, focusing on specific parts.

Understanding SCA is designed to be read in parts but also has a structure tying the various pieces together. The first chapter, "Introducing SCA," provides an overview of SCA and how it fits into today's technology landscape. The second chapter, "Assembling and Deploying a Composite," continues the overview theme by walking through how to build an application using SCA.

Chapters 3 and 4, "Service-Based Development Using Java" and "Conversational Interactions Using Java," respectively, turn to advanced SCA programming model topics. In these chapters, we detail how to design loosely-coupled services, asynchronous interactions, manage stateful services, and best practices for developing with SCA.

Having explored the SCA programming model in depth, Chapters 5–9 cover the main SCA concepts: composition, policy, wires, bindings, and the domain. In these chapters, we explain how to develop modular applications, use transactions, configure cross-application policies such as security and reliability, integrate with external systems, deploy applications, and structure corporate architectures using SCA.

Chapter 10, "Service-Based Development Using BPEL," demonstrates how to use BPEL with SCA to provide applications with long-running process capabilities.

The final two chapters round out application development with SCA by focusing on the data and presentation tiers. Chapter 11, "Persistence," details how to use Java Persistence API (JPA) with SCA to read and write data from a database. Chapter 12, "The Presentation Tier," demonstrates how to integrate web applications, in particular servlets and JSPs, with SCA services.


© Copyright Pearson Education. All rights reserved.

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Review
  • Posted July 27, 2009

    more from this reviewer

    simpler to code

    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!

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Review

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)