Skip to content

Template Request: RabbitMQ (AMQP) #1253

Description

@maxdobler

Reason/Context

Please try answering few of those questions

  • Why we need this improvement?
    Because RabbitMQ is a widely used me message broker and many teams use it

  • How will this change help?
    RabbitMQ (AMQP) is not underrepresenated in the AsyncApi project

  • What is the motivation?
    Right now the documentation lacks information for AMQP and therefore this would help AMQP users to start with AsyncApi.
    AMQP is a more advanced use case, because we have exchanges and queues bound to these exchanges via routing key / headers.
    Documenting this isn't always clear and an template would make it easier for starting with it.

Description

Please try answering few of those questions

  • What changes have to be introduced?
    Add template with basic AMQP docu

  • Will this be a breaking change?
    No

  • How could it be implemented/designed?
    Example with one send and one receive operation, with topic exchange, queue and routing key binding.
    Maybe add an additional example for header exchanges and a header binding.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions