Developing a new API is very often a pleasant experience for developers. Without any legacy code, we engineers can choose our tooling, think through the design process to ensure an enjoyable end user experience, build on top of a serverless platform, and all of the other best practices learned through the ages. However, companies and bosses task many engineers with taking a legacy API and supporting, maintaining, or porting it to a new architecture. Given an already deployed production API that sees constant usage, porting to a serverless system can be akin to changing the engine of a race car while in the middle of a race.
Fortunately, this complicated task can be made much simpler nowadays using the proxy pattern, the idea of which has been around for many years as a software pattern. If the name isn't clear enough, the main ideas are that a layer sits in between the client and backend system, which acts as a proxy, shuffling data...