System I have in mind is partitioned into disjoint pods for horizontal scalability. Data and behavior is partitioned by user. That said, any pod can receive requests for any user because the website is geo-load-balanced.
The API Gateway in each pod needs to do some intelligent routing based on the authenticated user’s username. The user to pod mapping needs to be dynamic - it could be cacheable for period of time for performance reasons. The authenticated user’s name is typically available in a JWT token, and the mapped pod is evaluated with a lambda expression.
Can Tyk be configured to perform routing in a more dynamic fashion to meet these requirements?
If this is already possible, I am curious to know details (was not obvious in docs) - please feel free to correct my tag to the question.