What is a server?
A server acts as a messaging broker system, establishing connections and facilitating communication between producers and consumers. Unlike traditional API servers that rely on request-response interactions, message broker interactions occur bidirectionally across various channels.
What is the purpose of servers?
Servers play a crucial role in establishing a connection between producers and consumers. In the context of designing and setting up an event-driven application, servers are responsible for delivering asynchronous messages from the producer to the consumers through the use of channels. Additionally, servers can integrate various messaging protocols to facilitate the transmission and exchange of messages between clients.
Clients and Server
The diagram above illustrates a bidirectional communication between one server and several clients. In this case, in your AsyncAPI file, you describe the server, so the Server Object holds information about the actual server, including its physical location.
Broker Centric
The diagram above illustrates the Broker-centric Architecture. In this case, there are three AsyncAPI files for the producer, consumer1, and consumer2. In these AsyncAPI files, the Server Object provides information about the broker, so that API users know where to connect to start receiving or sending messages.
