August 31, 2011
0 Comments
SOA is neither dead nor pining for the fjords. SOA can be done right, and is well worth doing right. You just won’t be able to do it if you let the OO heuristic community control the analysis and design.
(Full Story: When Acronyms Collide: SOA vs. OO – XML Today)
July 15, 2011
0 Comments
The third “leg” of the web services concept, Universal Description, Discovery and Integration (UDDI), conceptually makes a lot of sense, but in practice, hardly anyone uses it. As a developer, I couldn’t even think of a scenario where UDDI would help me in my particular project. Sure, I could artificially insert UDDI into my use case, but in the scenario where I needed loose coupling, I could get that by simply abstracting my end points and data schema. To the extent I needed run-time and design-time discoverability or visibility into services at various different states of versioning, I could make use of a registry / repository without having to involve UDDI at all. I think UDDI’s time has come and gone, and the market has proven its lack of necessity. Bye, bye UDDI.
(Full Story: How I became a REST ‘convert’)
May 16, 2011
0 Comments
Solution: A Service Virtualization infrastructure allows transparent service lookup and dispatch through an Enterprise Inventory, enforces policy through a policy enforcement point, employs elements of an ESB to handle service communication and leverages Redundant Implementation to achieve transparent quality of service management. The inventory architecture is equipped with policy processing and enforcement features.
(Full Story: SOA patterns: Service Virtualization)
April 1, 2011
0 Comments
Why the companies that really need service-oriented architectures are not likely to bite, and how they can be convinced.
One of the paradoxes of service-oriented architectures is that those companies that really could benefit from SOA are the ones not likely to adopt it. At the same time, the organizations that do aggressively embrace SOA probably don’t need it as badly.
What do I mean by this? As we found in the recent Webservices.Org survey, there were, out of 1,000 companies, only 50 that really were well advanced in their deployments, that could be considered true SOA sites. We parsed and dissected this “Fab 50″ group to see what made them so special.
(Full Story: The Rise of the JBOWS Architecture (or Just a Bunch of Web Services) / Joe McKendrick / weblog / WebServices.Org)
February 21, 2011
0 Comments
February 11, 2011
0 Comments
Governance encompasses more than just technology — it also includes people and processes. The WSO2 Governance Registry provides just the right level of structure — straight out of the box — to support your team in working together. Today you may have an ad-hoc process and “register” your enterprise services with a shared spreadsheet, which is a good start! But the WSO2 Governance Registry helps you move to the next level — understanding of the state and scope of your SOA, communicating and managing the lifecycle of your services, and finding the dependencies between services and consumers.
To begin, simply upload WSDLs, XSDs, WS-Policy documents, and other artifacts that you want to share. The Governance Registry’s Web interface will prove easy and familiar. You can think of it as something like a structured Wiki for SOA metadata.
(Full Story: WSO2 Governance Registry)
