Skip to content
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

Open
iluwatar opened this issue Oct 15, 2023 · 5 comments
Open

Microservice pattern: Messaging #2681

iluwatar opened this issue Oct 15, 2023 · 5 comments

Comments

@iluwatar
Copy link
Owner

iluwatar commented Oct 15, 2023

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:

  • Message Producers: Services that create and send messages.
  • Message Consumers: Services that receive and process messages.
  • Message Broker: Middleware that routes messages between producers and consumers, ensuring reliable delivery.

References:

Acceptance Criteria:

  1. Implement message producer and consumer services using a message broker such as Apache Kafka or RabbitMQ.
  2. Ensure that the system can handle asynchronous communication and maintain message integrity and reliability.
  3. Provide comprehensive unit and integration tests to verify that messages are correctly produced, routed, and consumed.
@pandiandk
Copy link

I am working on this

@pandiandk
Copy link

@iluwatar Could you please assign this to me ? already raised the PR :)

@iluwatar iluwatar moved this from Todo to In Progress in Java Design Patterns project Oct 22, 2023
pandiandk added a commit to pandiandk/java-design-patterns that referenced this issue Nov 2, 2023
-- refactoring source, test
-- clean up in pom file
-- updated comments in source
-- refactoring the readme wiki
Copy link

stale bot commented Dec 21, 2023

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.

@stale stale bot added the status: stale issues and pull requests that have not had recent interaction label Dec 21, 2023
@stale stale bot removed the status: stale issues and pull requests that have not had recent interaction label Mar 24, 2024
@iluwatar iluwatar moved this from In Progress to Todo in Java Design Patterns project Mar 24, 2024
@c99SRS
Copy link

c99SRS commented Oct 1, 2024

@iluwatar can you please assign this to me? I think I can do this by my backed domain expertise

@akshay-siddhpura
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

4 participants