Breaking down large APIs into smaller subsets using proxies

In recent times, one of the buzzwords in the industry has been microservices, where we develop our web components as microservices that can be managed (scaling, deployment, and so on) individually without impacting the other related components. Although the subject of microservices is itself a huge one, in this recipe, we'll try to build a few microservices that can be managed individually as independent function apps. However, we'll expose them to the external world as a single API with different operations with the help of Azure function proxies.

Getting ready

In this recipe, we'll be implementing the following architecture:

Figure 11.32: Azure function app with proxies—architecture

As depicted in the preceding architecture diagram, we are going to create three proxies in the gateway function app, which will be consumed by the client apps. Each proxy is responsible...