Open iluwatar opened 1 year ago
I am working on this
@iluwatar Could you please assign this to me ? already raised the PR :)
This issue has been automatically marked as stale because it has not had recent activity. The issue will be unassigned if no further activity occurs. Thank you for your contributions.
@iluwatar can you please assign this to me? I think I can do this by my backed domain expertise
Hi, I’d like to take on this issue. I’m familiar with implementing messaging systems using Kafka/RabbitMQ and can ensure the asynchronous communication and message integrity as required. I'll also write the necessary unit and integration tests to validate the functionality. Please let me know if there are any specific guidelines or requirements for the implementation.
Thanks!
@c99SRS are you still working on it?
@iluwatar Hi, I’d like to take on this issue. I’m familiar with implementing messaging systems using Kafka/RabbitMQ and can ensure the asynchronous communication and message integrity as required. I'll also write the necessary unit and integration tests to validate the functionality. Please let me know if there are any specific guidelines or requirements for the implementation.
Thanks!
thanks @iluwatar for assigning. I have started working on this.
This issue is stale because it has been open 60 days with no activity.
I would like to work on this! @iluwatar
Description:
The Microservices - Messaging design pattern enables microservices to communicate with each other through asynchronous message passing, allowing for better decoupling and scalability. This pattern involves the use of a message broker to facilitate communication between services, ensuring that messages are delivered reliably even if some services are temporarily unavailable. The main elements of this pattern include message producers, message consumers, and the message broker.
Key elements:
References:
Acceptance Criteria: