Enterprise Messaging and Eventing - amitbhilagude/userfullinks GitHub Wiki

  1. Messaging vs Eventing

    Messaging is pull based and need schedule to pull message. Eventing is reactive messaging automatically triggered.

  2. Service bus vs Storage queue Service bus supports message size upto 1 mb, additional features like dead latters, topics , subscriptions and reliablity.

  3. Service bus explorer Good tool for Service bus, Relay and Event Hub

  4. Azure relay

    1. Hybrid connection (Latest offering)
      1. Point to point connection
      2. File which sends is called listener and it needs to always in listening mode. Sender can send request to get that file.
      3. What is best practice to keep listener running mode for sending file to on-prem to cloud?
      4. What is best practices to keep listener running mode in cloud and sender request from on-prem?
      5. We can have load balancing by creating multiple listeners .https://www.serverless360.com/blog/understanding-azure-relay
    2. WCF Relay (Formally known as Service Bus Relay)
      1. Old offering of Azure Service Bus Relay
      2. Need to WCF Services on On-prem.

  5. Event Grid

    1. Reactive event processing to the service inputs
    2. Topics subscriptions also supported

  6. Event Hub

    1. Series of event processing, it uses underline storage account for storing events.
    2. Needs to create namespace, Throughput, Event hub with Partitions.
    3. We can use .net sdks to publish events or receive them.
    4. Second option is use Stream analytics to transfer events in SQL, or power BI.

  7. Comparison https://docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services

Hybrid connection types

  1. App Service Hybrid connection
  2. Virtual Network Hybrid connection
  3. Azure Relay Hybrid connection