Solace REST messaging uses bidirectional HTTP POST requests to exchange messages with Solace PubSub+ message brokers. This lets REST clients send and receive messages to and from other Solace PubSub+ message broker clients whether they’re using a Solace API or an open API or protocol. REST producers send message contents in the body of an HTTP POST request. For request / reply scenarios, the response contents are carried in the body of the HTTP 200 OK responses. For REST consumers, the message broker sends the message in the body of an HTTP POST request. And again for request / reply scenarios, the response contents are carried in the HTTP 200 OK responses. This is explained in more detail in REST Messaging Protocol. The use of bidirectional HTTP POST requests has several benefits. First it removes the possibility of message loss which can exist when using HTTP GET requests to poll for messages. It also enables much higher performance and overall message rate when multiple, parallel HTTP connections are used.
Tutorials are provided on the Solace Developer portal to introduce you to the fundamentals of using REST to develop applications using Solace PubSub+.