We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In order to allow usage of NATS through MiroProfile-base application, an integration with smallrye-reactive-messaging (github.com) would be beneficial.
github.com
Usage of NATS through the MicroProfile Reactive Messaging specification (github.com).
There is already smallrye/smallrye-reactive-messaging#1158 with some prelimiary work. The smallrye team is explicitly looking for contributors with NATS experience (github.com).
All java-applications using MicroProfile Reactive Messaging.
Provide/implement a corresponding connector separate from smallrye.
The text was updated successfully, but these errors were encountered:
Hi, there is a recent Quarkus extension that do the job for Nats Jetstream: https://github.com/quarkiverse/quarkus-reactive-messaging-nats-jetstream It may still benefits the eye of a Nats expert.
For non-jetstream cases, there is a Nats component available in Apache Camel which is available with SmallRye Reactive Messaging.
Sorry, something went wrong.
No branches or pull requests
Feature Request
In order to allow usage of NATS through MiroProfile-base application, an integration with smallrye-reactive-messaging (
github.com
) would be beneficial.Use Case:
Usage of NATS through the MicroProfile Reactive Messaging specification (
github.com
).Proposed Change:
There is already smallrye/smallrye-reactive-messaging#1158 with some prelimiary work. The smallrye team is explicitly looking for contributors with NATS experience (
github.com
).Who Benefits From The Change(s)?
All java-applications using MicroProfile Reactive Messaging.
Alternative Approaches
Provide/implement a corresponding connector separate from smallrye.
The text was updated successfully, but these errors were encountered: