Could the API Gateway criterion be expanded to a separate section to evalulate common features serverless developers need?
Here's a list of capabilities developers often need....
Rate limiting.
User authenticaiton & OAuth.
CORS support.
Path routing and named parameters.
Traffic shaping between versions.
API Gateway integration seems to vary between providers feature-wise. Comparing just on "function invocations from HTTP requests" might be less helpful.
disclosure: I work for IBM as an advocate for serverless and am an openwhisk committer.
Added everything you listed. As far as named parameters, I am wondering if I should just add about using wildcard as an evaluation feature than going deep on it?
Could the API Gateway criterion be expanded to a separate section to evalulate common features serverless developers need?
Here's a list of capabilities developers often need....
API Gateway integration seems to vary between providers feature-wise. Comparing just on "function invocations from HTTP requests" might be less helpful.
disclosure: I work for IBM as an advocate for serverless and am an openwhisk committer.