Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] Defining Jakarta EE 12 Scope in Program Plan: JMS
,

On Wed, 30 Oct 2024, 18:17 Kito Mann via jakarta.ee-community, <jakarta.ee-community@xxxxxxxxxxx> wrote:
Why does modernizing Messaging matter?

JMS has been one of the key specifications in Java EE. It was virtually synonymous with messaging in Java for a long time. ... In past years, Kafka has largely replaced JMS for Cloud Native messaging. ... Messaging must be urgently modernized to address these problems.

I've been wondering about this for quite some time. Is it possible to extend JMS so that it works for Kafka and perhaps cloud message services? That would make it very relevant again. It looks like Spring Messaging handles Kafka.

___

Kito D. Mann | @kito99@mastodon.social | LinkedIn
Java Champion | Google Developer Expert Alumni 
Expert consulting and training: Cloud architecture and modernization, Java/Jakarta EE, Web Components, Angular, Mobile Web
Virtua, Inc. | virtua.tech
+1 203-998-0403

* Enterprise development, front and back. Listen to Stackd Podcast.
* Speak at conferences? Check out SpeakerTrax.
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community

Back to the top