Micro-service architectures tend to have very large number of backend services, frontend APIs acting as the facade (Products) and API operations (mapping rules). This is currently supported by the APIs as a Product architecture but there are limitations with regards to how large these configurations can get. The request is to be able to support use cases such as that described in THREESCALE-5645 and even bigger. Typically in large installations we are seeing hundreds of services (can be reduced to dozens in an APIaaP arch.) and thousands of mapping rules in any given service. APIs as a Product should be able to support thousands of Products and thousands of mapping rules per Product.