AsyncAPI – OpenAPI-like specification for event-driven architectures

Re:AsyncAPI – OpenAPI-like specification for event-driven ar... by MuffinFlavored on Monday March 30, 2020 @05:08PM (#22732324)

I don't quite get it. Why can't I just enforce schema validation in my pub/sub handlers?

I see the YAML example completed here: https://www.asyncapi.com/docs/getting-started/servers/

    asyncapi: 2.0.0
    info:
      title: Hello world application
      version: '0.1.0'
    servers:
      production:
        url: broker.mycompany.com
        protocol: amqp
        description: This is "My Company" broker.
    channels:
      hello:
        publish:
          message:
            payload:
              type: string
              pattern: '^hello .+$'

This looks like a thin wrapper around sending a message to a message queue. What's the gain?

Where do you define what to do as a subscriber?

[ Parent | on HN ]

Re:AsyncAPI – OpenAPI-like specification for event-driven ar... by derberg on Tuesday March 31, 2020 @02:32AM (#22735366)

you have 2 operations in the spec, publish and subscribe.

above example already tells you what to do as a subscriber, as the document you shared describes an application that publishes a message

[ Parent | on HN ]