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

Document best practices in routing client requests to a network of peers #454

Open
Mingela opened this issue Dec 19, 2023 · 0 comments
Open
Labels
I-peer Documentation specific to Iroha peers

Comments

@Mingela
Copy link

Mingela commented Dec 19, 2023

Initially refers to the issue hyperledger-iroha/iroha#4119
In case paginated queries are considered it's crucial to remain communicating with the same node

There 2 solutions basically:

  • Infrastructure balancing (proxy)
  • SDK/Client application balancing

We tried the first one in an internal project and it seems okay, though generally the best practice would be the second option to eliminate inconveniences listed there https://pauldally.medium.com/session-affinity-and-kubernetes-proceed-with-caution-8e66fd5deb05

SDK side balancing is available in Java SDK though it's incomplete for the use case mentioned hyperledger-iroha/iroha-java#399

For unwrapping the first solution some consultancy by DevOps may be needed

@nxsaken nxsaken changed the title Document recommendations/best practices in case a number of Iroha nodes is used by single client Document best practices in routing client requests to a network of peers May 20, 2024
@nxsaken nxsaken added T-cli CLI documentation infrastructure I-peer Documentation specific to Iroha peers A-important High-impact, important change and removed T-cli CLI documentation L-infrastructure A-important High-impact, important change labels May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I-peer Documentation specific to Iroha peers
Projects
None yet
Development

No branches or pull requests

2 participants