Hey, remember registries in the WS-* stack? Sure, it was that part that stores all those services, lets you look them up, and acts a a general clearing house for all that yummy WS-* enabled XML-goop. Centralizing that sort of thing gives you the nifty effect of having more governance and control over versions of those services.
Well, in the neck of the woods I hang out in, people are not too chummy with WS-* stuff. Indeed, folks like the simpler things: just throw some XML over HTTP, or if you’re feeling all uppity use APP.
Recently, of interest, are two new attempts at the old registry problem, with attention paid to the simple is beautiful approach while casting a sighing glance to standards and the larger SOA world.
You might call them human-friendly rather than machine friendly registries: Mule’s Galaxy and WSO2’s Registry.
To my mind, both come from the ESB-driven camp of SOA. This camp cares about the low-level idea of using an ESB as a messaging bus for the SOA. The WS-* standards used don’t matter so much as the bus, which is the core technology in this SOA camp. Compare to the WS-* standards being king in the more “traditional” SOA understanding.
As such, these two registries focus on things like APP, REST, and – golly! – even tagging. Their focus is on, sure, making it easy for code to access and use the registry, but the more important aspect is to pull in humans to sort through and use the registries.
We’ll see how it goes this time: “registry” doesn’t usually get people all hot and bothered, but maybe tagging and “social networking” services will.
Disclaimer: MuleSource and WSO2 are clients.
Technorati Tags: mulesource, soa, ws-*, wso2
Recent Comments