Interfaces

Intro

At present there is 3 interfaces:

• SDK (.NET): A wrapper around the AMQP connection that makes it easy to connect, disconnect, and provides strongly typed definitions of each message, with client-side validations.

• REST: A lightweight API suitable for moderate use (under 1,000 messages per second.) It doesn't provide all of the capabilities of the AMQP protocol capabilities (specifically peek-locking).

• AMQP: A direct connection into the Azure network, suitable for non-.NET clients, this provides the capability of sending or receiving messages but lacks easy connection interfaces, strongly typed definitions and client-side validations:

  • Python: https://docs.microsoft.com/en-au/azure/service-bus-messaging/service-bus-python-how-to-use-queues

  • Java: https://docs.microsoft.com/en-au/azure/service-bus-messaging/service-bus-java-how-to-use-queues

  • JavaScript/Node.Js: https://docs.microsoft.com/en-au/azure/service-bus-messaging/service-bus-nodejs-how-to-use-queues

  • PHP: https://docs.microsoft.com/en-au/azure/service-bus-messaging/service-bus-php-how-to-use-queues