In an attempt to 'increase performance', many people will try to hack around in JMS - thereby falling into the idempotent receiver trap by checking for duplicate message receipt. The consequence: scalability actually degrades!
Fortunately, the best way to enjoy reliable messaging is also the simplest one, and it scales linearly.
Review: Going from Architect to Architecting: the Evolution of a Key Role
4 Microservice Myths and How to Avoid Them
High performance JMS processing with XA
Transactions for the REST of us
Transactions for SOA