Servers

In the previous lesson, we learned how to create the definition of a simple Hello World application, so let’s take it from there.

In this article, we will learn how to add “servers” to our AsyncAPI document. Adding and defining servers is useful because it specifies where and how to connect. The connection facilitates where to send and receive messages.

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:
    subscribe:
      message:
        payload:
          type: string
          pattern: '^hello .+$'

We added a new section called “servers” in our AsyncAPI document.

You might have noticed that the example mentions “amqp”. This protocol is very common and was popularized by RabbitMQ (among others). You can use any protocol. For example, the most common are mqtt (widely adopted by the Internet of Things and mobile apps), kafka (popular for its streaming solution), ws (WebSockets are frequently used in browsers), and http (used in HTTP streaming APIs.)

Remember

The “servers” section defines where your application should connect to start sending and receiving messages.

  1. If you are using a broker-centric architecture such as Kafka or RabbitMQ, usually you specify the URL of the broker.
  2. If you have the classic client-server model such as for REST APIs, then your server should be the URL of the server.

Conclusion #︎

Now we know where to connect to start receiving “hello {name}” messages.

On the next chapter, you’ll learn how to add security requirements to a server.