Hi James,
Camel can help you with that. Looks like you got it covered. For persistence
you have a few choices, camel-jms, camel-jpa, camel-sql, depending on your
message. But ActiveMQ is probably your best bet. It also scales very well (you
can also cluster it) and is relatively easy to config
I have seen this kind of operation in place before - SMS providers for example
for event driven stuff across the solution boundaries using basically a
callback implementation
I would
* expose an http interface to my solution. I think it would be RESTian for the
usual reasons
* I would use som
Folks,
Another question along similar lines to the System architecture thread.
I need to provide an asynchronous web service that will accept calls
from a client, persist them somewhere, then asynchronously try to call
a corresponding web service implemented by a third party.
If the call succeeds
