I fully agree with @RuGI - the Java EE market is worth billions, the platform is amazing at what it does, and neither are going away soon, if at all.
As far as adopting it for the microservices paradigm goes - I think Thorntail (what was known as Wildfly Swarm) is a wonderful start, and it just gets better - Jakarta EE is a perfect example of the community taking things into its own hands when the official processes have proven to be too rusty and impotent to respond (and the stewards of those processes being negligent, we all know who I'm talking about here :smileywink:).
Just one note, @flozano - mind that that the one thing AMQ Interconnect doesn't have is support for JMS. It is simply a wire-protocol proxy, and as such has no notion of durability and transactions that the JMS standard prescribes. I think persistence and transactions are rather important concepts in messaging.
Since AMQP is just a wire protocol, it doesn't address the behaviour of clients. It doesn't define the concept of producers and consumers, it doesn't even distinguish between a JMS client and a JMS broker, much less address destination behaviour (in terms of what happens once a message is delivered). So naturally, it can't distinguish between such client functions. In consequence, this requires client APIs that simulate JMS using AMQP to use various "hacks" to implement behaviour like delivery acknowledgements, transaction boundaries, request-response, etc.
In other words, you could say JMS is layer 7, and AMQP is layer 3/4 on the OSI model.
A black cat crossing the street signifies that the animal is going somewhere.
[don't forget to kudo a helpful post or mark it as a solution!]
