For my link list, especially because how it categorises the various kinds of messages: [WayBack] Getting Started with Azure Event Grid Scenarios | Serverless360 Blog:
- messaging, which conveys an intent
- eventing, which conveys a fact
- series events, which represent a stream of events belonging together (like telemetry, logging, or streaming data)
- discrete events, which are independent, and report some type of state change
If you use Azure, these solutions then apply to the categories:
- messaging: Azure Event Bus
- series events: Azure Event Hub
- discrete events: Azure Event Grid
Related:
- [WayBack] In order event processing with Azure Functions – Jeff Hollan – Medium (here Azure Service Vus and Azure Event Hubs can ensure in-order processing of the messages or events)
- [WayBack] architecture – Mircroservices – Ordering of Integration Events – Software Engineering Stack Exchange
- [WayBack] “Serverless” CQRS using Azure Event Grid – CodeProject
- [WayBack] Azure messaging services comparison | Microsoft Docs
- Event Grid
- dynamically scalable
- low cost
- serverless
- at least once delivery
- Event Hubs
- low latency
- capable of receiving and processing millions of events per second
- at least once delivery
- Service Bus
- reliable asynchronous message delivery (enterprise messaging as a service) that requires polling
- advanced messaging features like FIFO, batching/sessions, transactions, dead-lettering, temporal control, routing and filtering, and duplicate detection
- at least once delivery
- optional in-order delivery
- Event Grid
- [WayBack] Kafka 1.1 support on Azure HDInsight | Azure updates | Microsoft Azure
–jeroen
