When you say "SOA with JXTA", I'm assuming that you mean "SOAP over JXTA", as in: https://soap.dev.java.net/
It's been years since I've done this but the general result was less than what I'd hoped for. In some ways, JXTA is designed for the worse case scenario. That is, it is more about resilience than high throughput or low latency. Generally speaking, resilience isn't the primary non-functional requirement in business systems. JXTA assumes that you might have firewalls, NAT's and other ugly stuff in your network and is designed to traverse the obstacle, at the expense of speed and latency. It has been my experience that architects prefer to use alternative mechanisms to increase reliability and availability. I don't want to discourage anyone from going down this path, just encourage you to force-rank your non-functional requirements. Here's an article I wrote 7 years ago on the subject :-) http://www.openp2p.com/pub/a/p2p/2001/07/20/convergence.html Jeff Schneider --- In [email protected], henryk mozman <[EMAIL PROTECTED]> wrote: > > Has anyone in this group any experience in implementing SOA with the peer-to-peer > JXTA ? > > I would be interested in reading about your experience > > > Henryk >
