Our prior example is a best-case scenario. Because our new backend system included all of the data we needed to support our legacy API, our jobs were pretty easy. However, what happens in cases where the legacy API you need to support does not have a one-to-one mapping with a newer API? Of course, if you control the new API it's possible to implement any missing functionality. While that may be possible, it may not be a good idea since you may be reimplementing imperfect design in your new and clean RESTful API in order to support a legacy system.
In this case, rather than dirtying the new API, it's possible to use a Lambda function as the Integration Type, rather than an HTTP endpoint. With this pattern, the Lambda function may act with some intelligence and perform any type of task that is needed. For example, imagine another...
