Servers

Found an error? Have a suggestion?Edit this page on Github

On this page

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

In this article, you learn how to add servers to your 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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
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 .+$'

You added a new section called servers in your 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 you know where Hello world application app connects to, to start receiving hello {name} messages.

In the next chapter, you'll learn how to add security requirements to a server.