-
-
Notifications
You must be signed in to change notification settings - Fork 26.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microservice pattern: Messaging #2681
Comments
I am working on this |
@iluwatar Could you please assign this to me ? already raised the PR :) |
-- refactoring source, test -- clean up in pom file -- updated comments in source -- refactoring the readme wiki
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? |
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:
The text was updated successfully, but these errors were encountered: