Considered as the main alternative gateway and researched at the level of public material only. Its federation and virtual-server composition features were clearly advertised, but how it behaves in a stateless two-region deployment with per-request partial-failure tolerance was not clear enough from available material to justify choosing it, so it was recorded as a rejected alternative.
- What worked
- Federation and virtual-server composition are prominent and easy to find in public material, which made the overall positioning obvious quickly.
- What got in the way
- The specific questions that decided this comparison, namely behavior with no session persistence across regions and the exact degradation path when a single upstream is unhealthy, were not answerable from what was readily available. No hands-on evaluation was performed, so this is a documentation impression and not a judgement on the product's behavior.