Funny but i never thought of SOA as somehow separate from the Web. A Web-Stack is how one connects the disparate backend data streams. New applications capable of acting on that data are written to the Web, not some aging client/server platform model. I guess others had a different view of SOA and are just now discovering the interop and exchange value of the Web. Very strange.
This link has been bookmarked by 1 people . It was first bookmarked on 21 Apr 2008, by Gary Edwards.
-
21 Apr 08
Gary EdwardsThe Apache CFX "Interoperability Framework" for SOA Project is ready. We really could have used CFX in the 2003 Comcast project where a Tomcat/MYSQL Web-Stack connected to many disparate blackboxes. The blackboxes were standalone "Inventory and Billing" transaction processing data centers aquired by Comcast during a five year burst of acquisitions. Of course, none of these blackboxes could talk to any other! Enter SOA with XMLHTTPRequest streams. 2002-2003. We needed CFX to scale!
-
CXF is really designed for high performance, kind of like a request-response style of interaction for one way, asynchronous messaging, and things like that. But it’s really designed for taking data in from a variety of transports and message formats, such as SOAP or just raw XML. If you bring in the Apache Yoko project, we have CORBA objects coming in off the wire. It basically processes them through the system as quickly as possible with very little memory and processing overhead. We can get it to the final destination of where that data is supposed to be, whether it’s off to another service or a user-developed code, whether it’s in JavaScript or JAX-WS/JAXB code.
That’s the goal of what the CXF runtime is — just get that data into the form that the service needs, no matter where it came from and what format it came from in, and do that as quickly as possible.
-
Add Sticky Notethe fascinating intersection of SOA and WOA — with on-premises services and cloud-based resources (including data) supporting ecologies of extended enterprises business processes
-
-
Creating federated relationships between private and public clouds and their services and resources requires more than just industry standards. It requires visibility and access, the type that comes from open source communities and open use licenses.
-
Public Stiky Notes
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.