Abstract

Providing sandbox environments that closely mirror production for multi-tenant application programming interface (API) platforms may present challenges such as increased costs, architectural drift, and a risk of production contamination. A technical architecture may isolate stateful test accounts within a live production environment. A system can involve provisioning accounts with a persistent test attribute, using a declarative, fail-closed gating system to control API method access, and implementing a downstream publication sink filter. The gate can block test accounts from un-annotated methods by default, and the sink filter can prevent test-generated data from reaching consumer-facing surfaces. This approach can provide a testing environment that mirrors the production stack, which may reduce costs associated with separate clusters while programmatically mitigating the risk of live system impact.

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.

Share

COinS