-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
Comments
Hey @iluwatar , I would like to take up this issue. |
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. |
still working on it, the stale label can be removed |
This issue is stale because it has been open 60 days with no activity. |
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! |
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:
References
Acceptance Criteria
The text was updated successfully, but these errors were encountered: