Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
╔══════════════════════════════════════════════════════╦═════════════════════════════════════════════════════════════════════════╗
║ Lambda-Proxy ║ Lambda ║
╠══════════════════════════════════════════════════════╬═════════════════════════════════════════════════════════════════════════╣
║ 1. Very Easy to setup. Status code and the response ║ 1. It completely decouples the APIGateway from Lambda's request ║
║ message are in lambda's control. ║ and response payload, its headers and statusCodes. Thus, you ║
║ ║ have more control over the workflow. ║
║ ║ ║
║ 2. Easy for rapid prototyping, as you don't want ║ 2. Provides a procedural way of defining various status codes and error ║
║ to setup any APIGateway's settings. ║ messages. ║
║ ║ ║
║ ║ 3. The settings can be easily exported as Swagger specification, which ║
║ ║ makes documentation and generation of SDK much easier. ║
╚══════════════════════════════════════════════════════╩═════════════════════════════════════════════════════════════════════════╝
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment