You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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:
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
The text was updated successfully, but these errors were encountered: