Mesos has an API so that developers can build custom frameworks to run on top of the infrastructure. As you can imagine, Mesos implements the actor model for message passing, because the complexity increases without a non-blocking communication. This also leverages protocol buffers.
Support for the new HTTP API was introduced in the Mesos version 0.24. The Mesos Master has the /api/v1/scheduler endpoint which the scheduler communicates.
For detailed information about the scheduler HTTP API, go to:
http://mesos.apache.org/documentation/latest/scheduler-http-api/
The master accepts the following request calls.
To enable communication with the master, the scheduler sends a SUBSCRIBE message via HTTP POST. The response contains the subscription confirmation and the framework ID to continue the conversation.
The SUBSCRIBE JSON request structure is:
POST /api/v1/scheduler HTTP/1.1 {
"type" : "SUBSCRIBE",
"force" : true,
...