Complementary or incompatible: ServiceBus , OData/OAuth RRS feed

  • Question

  • Are OData/OAuth and ServiceBus complementary or mutually exclusive, and why? I don't find any combined usage off hand, so I am assuming there is a reason for this. If not reasonably used together, why not? Orthogonal or competing (overlap).

    Thanks for helping clear this up!

    Wednesday, November 26, 2014 3:51 PM


All replies

  • Hi Hubert,

    I don't think OData/OAuth has the same function with the service bus. OData is to provide a REST-based protocol for CRUD-style operations. OAuth  focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices.

    But the Microsoft Azure Service Bus provides a hosted, secure, and widely available infrastructure for widespread communication, large-scale event distribution, naming, and service publishing. They have the different role.


    Monday, December 1, 2014 2:48 AM
  • ServiceBus now is compound of several services: Relays, Queues, Topics, EventHub. 

    OAuth is used in Service Bus connections as one of the security method:


    In the first case, the authentication and authorization to use a service exposed by Service Bus are controlled either by a Shared Access Signature (SAS) token or by a token issued by the Access Control Service, and can be programmatically accessed through the Service Bus API. There are four types of authentication currently available:


    Here are some thoughts about using OData with ServiceBus

    In short words Service Bus can be used to help communicate with OData services using Relay service.

    Queue, Topics or EventHub can be used if you need to communicate with OData services asynchronously, which is kind of unnatural way to communicate with OData. 

    Leonid Ganeline [BizTalk MVP]

    Monday, December 1, 2014 4:49 PM
  • Leonid, thanks this has considerably cleared some of the smoke. the OData/OAuth value proposition is clear, as is that of a PubSub-Bus on its own. As cool as the "compound of services", as you aptly put it, is, we need to continue leveraging OData/OAuth if at all possible.... In short: as much as we appreciate the azure stack, we still need to pick a clean set of orthogonal services to avoid design chaos in our systems. After looking at the (only one since 2010?) topic you refer too, it appears that they can coexist and be complementary to solve some realistic use cases. Any other pointers or tips to further clear this up would be greatly appreciated.

    Monday, December 1, 2014 8:24 PM
  • Let's look at it from another perspective.

    OData is about exposing DB through REST APIs. Azure Service Bus is not about data bases. There are another data base Azure services should be considered in relation to OData.

    OAuth can be used inside Azure stack in almost any Azure services.

    So, the short answer is: Service Bus, OData and OAuth are complimentary and independent.

    Leonid Ganeline [BizTalk MVP]

    Monday, December 1, 2014 9:44 PM