I wasn't thinking of something low-level and network-protocol-based, although I'll certainly look into it, and it might be useful for internal applications that need high-performance networking. Thanks for the tip.
Rather, I was wondering if an Enterprise Service Bus or something like that would help us with thing like: - Keeping a central registry of services - Relating persistent session data with incoming and outgoing messages via some sort of job ID passed between services - Applying XML transformations to messages going between services All the while using standard SOAP over standard HTTP over standard TCP, to enable interoperability with remote services. Are there existing frameworks that are designed for this kind of meta service architecture? Andrew. 2009/1/17 jian wu <[email protected]>: > Hi, > > If I understand correctly, what you want to build can be categorized > as a Web Service Gateway or more generally a Service Gateway. > > You might want to check Apache MINA ( http://mina.apache.org/ ), which > is a very good NIO based framework to build Service Gateway. > > Hope this info would be helpful. > > Jian > > > On Wed, Jan 14, 2009 at 2:20 AM, Andrew Clegg <[email protected]> wrote: >> Morning all, >> >> I have a slightly fuzzy question that I'd appreciate any feedback on. >> >> I'm working on a CXF-driven distributed app for analysing molecular >> biology data, consisting of a user-facing front-end web service that >> routes requests in parallel to various other services. Some of these >> are also written in CXF and hosted locally, some are at remote sites >> and use Perl, and potentially other platforms. All of these component >> services (so far) use basically the same WSDL, as they perform >> functionally analogous operations on the data but using different >> algorithms. >> >> The front-end service is quite complex and does things like: managing >> persistent user sessions, keeping track of which component services >> are online, asynchronous job handling, transforming inbound requests >> from users into outbound requests to the other services using XSLT, >> parsing and generating XML (too much data for efficient databinding), >> plus the domain-specific stuff e.g. stats on the data. >> >> My question is: is this the kind of thing that people use some of the >> frameworks in the Subject line for? >> >> As it stands, I've "rolled my own", since this is the first Java SOA >> project I've worked on, and it works pretty well so far, but it's >> approaching the level of complexity where I'm wondering if an ESB or >> similar would have helped. >> >> If anyone has any feedback on using technologies like these in >> similarly-structured projects, or pointers to blog posts or other >> useful resources, I'd be really glad to hear them. At the moment I >> only have the vaguest idea of how all these products relate to each >> other, and wouldn't know how to choose one over another if it came to >> that. >> >> The project homepage is at http://funcnet.eu if anyone's interested. >> >> Thanks in advance! >> >> Andrew. >> >> -- >> New site launched: http://biotext.org.uk/ >> >> I am retiring my old email addresses. >> Please use [email protected] where firstname = andrew. >> > -- New site launched: http://biotext.org.uk/ I am retiring my old email addresses. Please use [email protected] where firstname = andrew.
