One of the prerequisites for successful SOA implementations is service repository–a place to store and track changes of the existing Services portfolio. In his article Ben Wilcock describes shortcomings of existing commercial and open source implementation and proposes a simple Service Registry implementation. He also outlines how such repository can be leveraged is SOA delivery process.
Karl Pauls has released PojoSR 0.1.6, a service registry that enables OSGi bundles to be loaded and services wired together without the need for a full OSGi runtime stack. PojoSR differs from the full OSGi platform in that it does not use nested classloaders; so badly behaved libraries like Hibernate – which are often tripped up in a structured OSGi environment – continue to work as normal.
Yesterday, Microsoft released .Net RIA Services which was mostly in stealth mode until now. In his presentation at MIX 09, Nikhil Kothari, explained "n-tier development and architecture is hard and un-natural. Our goal is to bring ASP.NET / RAD style productivity to RIA developmend"
After the Oracle acquisition of BEA it was not clear how Oracle was going to integrate often competing SOA products in its and BEA’s portfolio. In his presentation last month David Shaffer, VP Product Managemen for, Oracle Integration, described the Oracle-BEA product Strategy and Roadmap for SOA, BPM, Governance and Events.
Service Discovery is an essential aspect of service orientated architecture because it avoids early binding of clients to particular service instances. In this article, Jan Algermissen explains the need for discovery of RESTful services, and explains how the existing Domain Name Service (DNS) standard can be used as a widely-deployed and scalable solution.
In this article, Boris Lublinsky explains the design and implementation of a service registry that decouples service consumers and providers in a .NET-based SOA environment. The registry endpoint addresses and binding types, and additional configuration parameters, for example send/receive timeouts, message sizes, at runtime.
Paul Mooney attempts to clear up some of the misunderstandings surrounding SOA considering the fact that many implementations are labeled as “SOA” but are not. He does that by describing an SOA journey from establishing a route (characteristics, goals, benefits), planning it (service inventory), making it (service design) and arriving at the destination (measuring success, governance).
