Currently, the architectural direction from our company is to use JMS for communication between processes internal to the company.
We are designing a service, whose consumers will use the service Synchronously. So, the consumers will send a message via JMS to the service and then wait on another queue using a JMS selector.
Does anyone, have any opinions or advice on this topic . Iam looking for advice related to best practices, performance, etc ..
posted 4 years ago
We have implemented a distributed processing system using JMS (inter-jvm work with optional synchronicity, time-outs, error handling, etc.). It is quite complex and wasn't easy, but it works reasonably well. Some clustering technologies like Terracotta offer similar capabilities, but have their own pains to bear.
I don't think your use case is quite as demanding as ours, so jms might well be a good solution for you. The other possibility you may want to consider is using a lightweight web service like REST.