Service Bus

1) Microsoft Azure Service Bus is a fully managed enterprise integration message broker.


2) Microsoft Azure’s Service Bus is a cloud service that helps facility the ability to share data between decoupled systems.

3)Reliable cloud messaging as a service (MaaS) and simple hybrid integration

 

 

Some common messaging scenarios are

  • Messaging. Transfer business data, such as sales or purchase orders, journals, or inventory movements.
  • Decouple applications. Improve reliability and scalability of applications and services. Client and service don't have to be online at the same time.
  • Topics and subscriptions. Enable 1:n relationships between publishers and subscribers.
  • Message sessions. Implement workflows that require message ordering or message deferral.

Fundamentals of Service Bus

Namespaces

A namespace is a container for all messaging components. Multiple queues and topics can be in a single namespace, and namespaces often serve as application containers.

Queues

Messages are sent to and received from queues. Queues store messages until the receiving application is available to receive and process them.Messages in queues are ordered and timestamped on arrival. Once accepted, the message is held safely in redundant storage. Messages are delivered in pull mode, only delivering messages when requested.

Topics

You can also use topics to send and receive messages. While a queue is often used for point-to-point communication, topics are useful in publish/subscribe scenarios.

 

Topics can have multiple, independent subscriptions. A subscriber to a topic can receive a copy of each message sent to that topic. Subscriptions are named entities. Subscriptions persist, but can expire or autodelete.

 

You may not want individual subscriptions to receive all messages sent to a topic. If so, you can use rules and filters to define conditions that trigger optional actions.

Advanced features

  1. Message sessions

  2. Autoforwarding

  3. Dead-letter queue

  4. Scheduled delivery

  5. Message deferral

  6. Batching

  7. Transactions

  8. Filtering and actions

  9. Autodelete on idle

  10. Duplicate detection

  11. Security protocols

  12. Geo-disaster recovery

https://www.e4developer.com/2018/01/28/setting-up-rabbitmq-with-spring-cloud-stream/

Made with Slides.com