Skip to content

Instantly share code, notes, and snippets.

@tj

tj/lambda.md

Last active May 29, 2020 16:06
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save tj/f9f192e00baa6b7aa94434653575b4c7 to your computer and use it in GitHub Desktop.
Save tj/f9f192e00baa6b7aa94434653575b4c7 to your computer and use it in GitHub Desktop.
Download ZIP
Lambda proposal
Raw
lambda.md

The goal is for the next version of Up to provide all of the runtimes which Lambda already supports. Up lets users write regular HTTP servers, using any framework they prefer. Up works by translating Lambda events to and from HTTP requests, using a Go proxy inside of the Lambda.

Currently Lambda imposes limitations which prevent this from working well with all runtimes, since the Go proxy needs to be the handler, while the runtime files/interpreters still need to be present.

I see two solutions to this problem, the first is to expose the existing runtimes as layers, allowing the proxy to live in a "provided" runtime, but still reference the others for their files. The second is to allow layers to act as the entrypoint/bootstrap, while still allowing the user to select an existing runtime as they normally would, just giving precedence to the layer.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment