{"id":3493,"date":"2021-09-03T13:59:00","date_gmt":"2021-09-03T11:59:00","guid":{"rendered":"https:\/\/blog.besharp.it\/?p=3493"},"modified":"2024-02-02T11:59:58","modified_gmt":"2024-02-02T10:59:58","slug":"how-to-integrate-legacy-api-with-aws-api-gateway-proxy","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/how-to-integrate-legacy-api-with-aws-api-gateway-proxy\/","title":{"rendered":"How to Integrate legacy API with AWS API Gateway proxy"},"content":{"rendered":"\n
The emergence of modern web and mobile applications, based on microservices exposing HTTP APIs, has highlighted the need to effectively integrate, deploy, decommission, throttle, and securing a plethora of heterogeneous web APIs. This is mostly due to the inherent inhomogeneity of backend resources allowed and encouraged by the microservice pattern: each microservice composing a complex application may be developed and deployed in a unique way (programming language, deployment platform, etc) and some of them may even SaaS APIs, completely outside the direct control of the company developing the application as a whole.
<\/p>\n\n\n\n
Several companies and open source initiatives have developed API gateway<\/strong> solutions in order to meet the above requirements and expose a coherent API format for all the microservices composing the application.<\/p>\n\n\n\n <\/p>\n\n\n\n