Hi, Team,
1. Does Apigee support 2 layers traffic policy below with Geolocation and Latency policies (each layer URL is usable)? How to configure Apigee accordingly? with Condition system.region.name and more?
1.1 for users in EU geography:
dev.non-prod.example.com -> dev.non-prod.ec1.example.com (Frankfurt)
dev.non-prod.example.com -> dev.non-prod.ew1.example.com (Ireland)
1.2 for users in APJ geography:
dev.non-prod.example.com -> dev.non-prod.as1.example.com (Singapore)
dev.non-prod.example.com -> dev.non-prod.an2.example.com (Seoul)
1.3 for users from the rest of the world:
dev.non-prod.example.com -> dev.non-prod.uw2.example.com (Oregon)
dev.non-prod.example.com -> dev.non-prod.ue1.example.com (Virginia)
2. Does Apigee support 3 layers traffic policy below with Geolocation and Latency policies (each layer URL is usable)? Nested? Stable? Costly? How to configure Apigee accordingly?
2.1 for users in EU geography:
dev.non-prod.example.com -> dev.non-prod.eu.example.com -> dev.non-prod.ec1.example.com (Frankfurt)
dev.non-prod.example.com -> dev.non-prod.eu.example.com -> dev.non-prod.ew1.example.com (Ireland)
2.2 for users in APJ geography:
dev.non-prod.example.com -> dev.non-prod.apj.example.com -> dev.non-prod.as1.example.com (Singapore)
dev.non-prod.example.com -> dev.non-prod.apj.example.com -> dev.non-prod.an2.example.com (Seoul)
2.3 for users from the rest of world:
dev.non-prod.example.com -> dev.non-prod.us.example.com -> dev.non-prod.uw2.example.com (Oregon)
dev.non-prod.example.com -> dev.non-prod.us.example.com -> dev.non-prod.ue1.example.com (Virginia)