In an InfoQ exclusive article, Mike Edwards discusses how to create asynchronous services within the Service Component Architecture.
With the advent of Spring and the development of the Dependency Injection pattern, Component Technologies have started providing advanced composition mechanisms. In the past month IBM and SAP published related articles exploring the modern strategies and tactics to develop composite business solutions.
Sun Microsystems started a tour in the US to present a comprehensive view of the technologies and approaches it recommends to build Service-Oriented-Architectures with Java Technology.
In a new InfoQ article, Jean-Jacques Dubray explores a new architecture blueprint for BPMSs that offers a cleaner alignment between SOA and BPM. Jean-Jacques argues that after more than eight years of intense research, we are still far from having the ability to use the business process models designed by business analysts to create complete executable solutions.
In a new InfoQ minibook, InfoQ SOA Editor and SOA Enterprise Architect Jean-Jacques Dubray describes the state of the art and emerging new approaches in building "Composite Software", solutions created by assembling existing services. The book is available as an InfoQ Minibook, i.e. free of charge in PDF format for InfoQ users. A printed version is available too.
Henning Blohm, Java EE Software Architect at SAP and Co-Chair of the SCA-J Technical Committee provides his perspective on SCA as a cross-technology programming model integration. He claims that for vendors SCA lowers the marginal costs of providing implementation or binding technology and for users it reduces the marginal costs of using them.
David Chappell, from Chappell & Associates, started a debate on SCA by reasoning that "Microsoft Should Not Support SCA".
InfoQ took time to talk to some of the driving forces behind SCA at the OpenCSA Plenary held recently.
The the Apache Software Foundation has released the first 1.0 implementation of the Service Component Architecture (SCA), Apache Tuscany 1.0. SCA is a set of specifications aimed at simplifying SOA Application Development which are being standardized at OASIS as part of Open Composite Services Architecture (Open CSA).
The Apache Tuscany team has released version 0.99 of its open source Service Component Architecture (SCA) implementation. InfoQ talked to Jean-Sebastien Delfino, one of the lead developers, about Tuscany, the parts of SCA that are missing, and the role of the assembly and programming models.
Less than a week after the official announcement concerning the formation of 6 new SCA-related technical committees, OASIS announces that there will be a 3 day Plenary, which will include an educational day followed by the first meetings of the various committees.
Eric Newcomer comments on David Chappells assertion that SCA participants have differing views about what aspects of SCA are important. In David's view it is the new Java programming model. Eric disagrees: in his view it's the service assembly model.
A case study about how motor vehicle insurance records company Safeco used SOA approahes, SCA, BPEL, and composite application approaches to reuse legacy code, enable runtime modifiability thanks to decoupling, Java and .NET interoperability, and the ability to deliver a complex solution integrating over 5 systems in less than 8 weeks with a small team.
In a panel on the Service Component Architecture (SCA) at JavaOne, one of the controversive topics was the SCA client programming model. Moderator David Chappell and Gregor Hohpe share their impressions.