Azure Messaging Paradigms
- Event Grid - Best suited for reactive programming (something happened here and somebody wants to know it)
- Event Hubs - Telemetry and distributed data streaming
- Storage Queues - just a queue. Once the messages are read, they will be removed from queue.
- Service Bus
- Multi tenant cloud message service that sends information between applications and services
- Queue, Topics and Subscriptions
- Publishers and Subscribers
- Queues
- Messages in the queue are ordered and timestamped on arrival. After that messages are saved safely in a redundant strategy so that it's not lost
- The receiver has to ASK for message
- Topics and Subscriptions
- Pub/Sub pattern
- Storage queue can grow more than 80 GB
- Service Bus can grow only upto 80 GB
- Service Bus guarantees FIFO, duplicate detection
- Create Service Bus Namespace
- eg: Mycompany.servicebus.windows.net
- Pricing tier
- Subscription
- Resource group
- Location
- Primary Connection string (to connect to the bus)
- Create queue
- Queue Name
- Size
- Topics and Subscriptions
- Subscribers are invoked or notified when a message of interest appears
No comments:
Post a Comment