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: Remote procedure invocation #2680

Open
iluwatar opened this issue Oct 15, 2023 · 5 comments · May be fixed by #3189
Open

Microservice pattern: Remote procedure invocation #2680

iluwatar opened this issue Oct 15, 2023 · 5 comments · May be fixed by #3189

Comments

@iluwatar
Copy link
Owner

iluwatar commented Oct 15, 2023

Description

The Microservices - Remote Procedure Invocation (RPI) design pattern is crucial for enabling microservices to communicate effectively in a distributed system. This pattern allows a program to cause a procedure to execute in another address space (commonly on another physical machine). The procedure call is abstracted to appear as a local function call, though it is executed remotely.

Main Elements of the Pattern:

  1. Service Definition: Defines the methods and parameters that can be called remotely.
  2. Client Proxy: Acts as a local representative for the remote service. It abstracts the complexity of remote communication.
  3. Network Protocol: Handles the transmission of requests and responses between client and server.
  4. Server Stub: Unpacks the requests, executes the corresponding service methods, and packs the results to be sent back to the client.
  5. Serialization/Deserialization: Transforms data structures or objects into a format that can be easily transmitted and reconstructed.
  6. Error Handling: Manages issues like network failures, timeouts, and service unavailability.

References

Acceptance Criteria

  1. Implement a basic example of the RPI design pattern demonstrating remote communication between microservices.
  2. Include comprehensive unit and integration tests to ensure reliable communication and proper error handling.
  3. Update the project documentation to include an explanation of the RPI pattern, its implementation details, and usage instructions.
@CoderSleek
Copy link

Hey @iluwatar , I would like to take up this issue.

Copy link

stale bot commented Dec 13, 2024

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 13, 2024
@CoderSleek
Copy link

still working on it, the stale label can be removed

@stale stale bot removed the status: stale issues and pull requests that have not had recent interaction label Dec 13, 2024
Copy link

This issue is stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the Stale label Feb 12, 2025
@iluwatar iluwatar moved this from In Progress to Todo in Java Design Patterns project Feb 16, 2025
@CoderSleek CoderSleek linked a pull request Feb 16, 2025 that will close this issue
4 tasks
@CoderSleek
Copy link

Hey @iluwatar, apologies for the long time I took to raise the PR it was work in progress. I have attached a PR that closes the issue, would like to request review

Help wanted label can be removed and can be assigned back to me!

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

Successfully merging a pull request may close this issue.

2 participants