Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat: initial WIP of the spec #3

Closed
wants to merge 4 commits into from
Closed

feat: initial WIP of the spec #3

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
853c536
feat: initial WIP of the spec
lholmquist Jul 5, 2023
435a015
squash: update overview
lholmquist Jul 5, 2023
54c032e
squash: moving things around
lholmquist Jul 6, 2023
5a87397
squash: some formatting
lholmquist Jul 6, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
squash: update overview
  • Loading branch information
@lholmquist
lholmquist committed Jul 5, 2023
commit 435a0159b533bd688589a86a7e08e3e38452f845
4 changes: 3 additions & 1 deletion spec/drafts/functions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,9 @@ A vendor-neutral specification for defining the function signature for serveress

## Overview

TODO
Today every competing JavaScript functions API is different enough that we end up with lower developer productivity and vendor lock-in. Lower developer productivity because developers have to learn multiple ways to write the JavaScript function code and may have to write more complex code to avoid vendor lock-in. Organizations wanting to leverage multiple functions providers or move from one provider to another incur significant additional cost.

The Goal is to define a JavaScript functions API that avoids vendor lock-in and facilitates developer productivity while being general enough to allow different implementations and optimizations behind the scenes.

### Out of Scope

Expand Down