river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [River Wiki] Update of "JavaBasedSOA" by GregTrasuk
Date Sun, 31 Jul 2011 23:02:14 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "River Wiki" for change notification.

The "JavaBasedSOA" page has been changed by GregTrasuk:
http://wiki.apache.org/river/JavaBasedSOA

New page:
= Java-Based Service Oriented Architecture =

Service Oriented Architecture (SOA) is a hot topic in the past few years.  When you say "SOA",
most people think in terms of XML-based web services (mostly SOAP on http) communicating through
an Enterprise Service Bus.  

There's a funny thing about it; people claim that one of the selling points is language-neutrality,
but they don't actually practice it.

If you ask corporations that are implementing SOA what languages they expect to be using to
implement their services, you get roughly the following responses (informal survey, of course)
 * 90% or so will say either Java or dot-Net
 * 5% or so will say Java for the business logic with dot-Net front-end
 * Maybe 5% will say they actually have a mix of languages in the SOA

So, people are mostly implementing SOA in Java, and yet, they spend huge amounts of effort
encoding all their interfaces in WSDL, defining all their data in XML Schema, and implementing
Enterprise Service Buses to provide protocol-neutral connectivity.

If it were easier to get up and running, Jini would be a great solutions for most current
users of SOA (we'll just ignore the fact that Jini predates current ideas of XML-based SOA).

The archetypal SOA looks like this:
{{attachment:ArchetypalSOA.png|Standard SOA with User interface talking to business process,
invoking services through ESB|width=800}}

Looking at this from a Jini/River perspective, we can make a few observations:
 * By decoupling service location through the registrar, and allowing for dynamically downloaded
proxies that implement whatever protocol the service wants, Jini makes most of the ESB functionality
(a magic connectivity cloud)  unnecessary.
 * Standard SOA's concept of 

Mime
View raw message