Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-15016

Provide full Support for MicroProfile Reactive Messaging for AMQ Streams (Kafka) integration

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • None
    • MP Reactive Messaging
    • None
    • 5
    • Documentation (Ref Guide, User Guide, etc.), Release Notes, Interactive Demo/Tutorial

    Description

      Sending and receiving messages between microservices using MicroProfile Reactive Messaging specification via Kafka/AMQ Streams.

      MicroProfile Reactive Messaging makes it easy to write and configure user application to send, receive, and process the stream of events efficiently and asynchronously.

       

      For EAP the main use-cases would be able to bridge reactive messaging to/from user code. Reactive Use case for EAP is limited to listen for/receive data and forward streams with some processing in the enterprise backend (EE) such as transactional data persistence. So, EAP is a message relayer; where it would have ability to consume messages from Kafka.  It will be possible to consume, process, and produce messages within your application.

      Smallrye Reactive Messaging: https://smallrye.io/smallrye-reactive-messaging/

       

      Supported in the platforms where both EAP and AMQ Streams [1]  are supported i.e. OCP and RHEL. 

       

       [1] https://access.redhat.com/articles/2791941

       

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users WFLY-14798 Upgrade to MicroProfile Reactive Messaging 2.0

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users WFLY-14932 Configuration of Reactive Messaging Kafka messages

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users WFLY-14987 Configure Reactive Messaging Kafka connector to use SSLContext from the Elytron subsystem and allow SASL_PLAINTEXT and SASL_SSL protocols

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              kkhan1@redhat.com Kabir Khan
              bozpeyni@redhat.com Bilgehan Ozpeynirci
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: