Performance Testing the Apollo Router - When, How and How much #4684
shnisheeth
started this conversation in
Implementation
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Apollo Router being one of the most critical components and almost a Single Point to Failure, meddling with every request and response - it makes this whole Architecture bit trickier and fairly cardinal to ascertain - When to Performance Test the Router, How to do it, How much is not Too much ?
Here is a Scenario , Personal Views and food for thoughts -
Thoughts -
When Subgraphs get developed, we should know how many consumers, what type of Queries (APQs), In Memory Caching , transactions per second requirements - we can always Load Test the Subgraphs in the Isolation and be happy about it .
Scenario- Say we have 4 Subgprahs, each supporting 2 APQs(s o say 8 of those) , each Subgraphs needing to support an average of 20 Transactions per second.
2 More Subgraphs with same Perf needs as earlier one are going to get added in a month or so, -
Questions-
Needed to hear your ideas , thoughts or experiences & is something that is much appreciated ....
Beta Was this translation helpful? Give feedback.
All reactions