This is how netflix approached api gateways. <a href="http:&#x2F;&#x2F;techblog.netflix.com&#x2F;2012&#x2F;07&#x2F;embracing-differences-inside-netflix.html" rel="nofollow">http:&#x2F;&#x2F;techblog.netflix.com&#x2F;2012&#x2F;07&#x2F;embracing-differences-in...</a><p>However, this approach is a giant pain in the ass and technologies like Falcor (netflix cannabilizing its own pattern) and (my preference) GraphQL will come to replace.<p>With a generic client side query language, you don&#x27;t need to deal with versioning APIs, lots of concurrent development, overhead of deploying a new API for each client, the list goes on. GraphQL in front of a set of services is how we&#x27;re approaching our next project and it&#x27;s working really well so far.