https://github.com/nurislom373/messagebrokers

Most popular message brokers integration with Java, Kotlin
https://github.com/nurislom373/messagebrokers

activemq kafka rabbitmq redis-queue spring-boot

Last synced: 3 months ago
JSON representation

Most popular message brokers integration with Java, Kotlin

• Host: GitHub
• URL: https://github.com/nurislom373/messagebrokers
• Owner: Nurislom373
• Created: 2022-08-16T13:30:24.000Z (over 2 years ago)
• Default Branch: master
• Last Pushed: 2024-06-05T17:41:42.000Z (8 months ago)
• Last Synced: 2024-06-05T19:58:09.654Z (8 months ago)
• Topics: activemq, kafka, rabbitmq, redis-queue, spring-boot
• Language: Java
• Homepage:
• Size: 933 KB
• Stars: 6
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
## Most popular message brokers integration with Java, Kotlin

1. Apache ActiveMQ

2. Apache Kafka

3. RabbitMQ

4. Redis Broker

# What is Message Broker

message broker is an intermediary program that applications and services use to communicate with each other to exchange information. Message brokers can be used to validate, store, route and deliver messages to the required destinations. Not only applications can communicate information, even if they are implemented in different programming languages. Since message brokers act as an intermediary program, the sender has no idea how many recipients there are if they are online.

Most importantly brokers ensure that recipients receive the message even if they are not online or active. (It’s kinda like email. You don’t have to be online but you still receive the message).

Message brokers use a message queue for this and it’s saved in memory or a hard disk. They are used to store messages and deliver them. (I hope you are familiar with the data structure “Queue”. This is the same as this, First In First Out).

Message queue stores messages in the exact order they are received and sends to the receiver in the same order. If somehow a message was unable to be delivered (problem with the network) the message will be rescheduled for later in the queue. Also in a message queue, messages are stored in the exact order in which they were transmitted and remain in the queue until receipt is confirmed.