Contents
How does RabbitMQ work?
The user sends a PDF creation request to the web application. The web application (the producer) sends a message to RabbitMQ that includes data from the request such as name and email. An exchange accepts the messages from the producer and routes them to correct message queues for PDF creation.
Why Kafka is better than RabbitMQ?
Kafka offers much higher performance than message brokers like RabbitMQ. It uses sequential disk I/O to boost performance, making it a suitable option for implementing queues. It can achieve high throughput (millions of messages per second) with limited resources, a necessity for big data use cases.
What’s the solution to the producer consumer problem?
The problem is to make sure that the producer won’t try to add data into the buffer if it’s full and that the consumer won’t try to remove data from an empty buffer. The solution for the producer is to either go to sleep or discard data if the buffer is full.
What’s the difference between a producer and a consumer?
The producer repeatedly generates data and writes it into the buffer. The consumer repeatedly reads the data in the buffer, removing it in the course of reading it, and using that data in some way.
How does a producer send data to a broker?
Case2: The producers send data to the brokers. Broker 1 holds the leader. Thus, the leader asks Broker 1 whether it has successfully received data. After receiving the Broker’s confirmation, the leader sends the feedback to the Producer with ack=1. Case3: The producers send data to each broker.
Can a consumer read into the same slot as a producer?
With multiple producers sharing the same memory space for the item buffer, or multiple consumers sharing the same memory space, this solution contains a serious race condition that could result in two or more processes reading or writing into the same slot at the same time.
https://www.youtube.com/watch?v=rKGq9AlfPR4