title: Local development of client and services against API Gateway
body: <p>When developing backend microservices that sit behind an API Gateway how do you develop locally, ensuring that client requests to a single endpoint (the API gateway) and request path are routed to the right local service?</p>
  
  <p>The Microsoft <a href="https://github.com/dotnet-architecture/eShopOnContainers" rel="nofollow noreferrer">eShopOnContainers</a> architecture example uses Envoy as a local API Gateway (it used to be Ocelot) but how would you then deploy a stack like this to the cloud, keeping your local and cloud API Gateways in sync with the right request routing, resource descriptions, etc? Do you essentially need to manage two API gateway configurations?</p>
  
  <p>I'm aware of SAM and <code>sam local start-api</code> but I'm referring to other backend services that aren't serverless, e.g. using <code>VpcLink</code>.</p>