3 ms·
Wouldn’t using a lambda for this be a good choice? You’re just parsing a input document into a set of backend requests and then executing them - there doesn’t h
by orf 5y ago
Wouldn’t using a lambda for this be a good choice? You’re just parsing a input document into a set of backend requests and then executing them - there doesn’t have to be anything stateful here that would require an actual running instance.
If you combine this with API-gateway you’ve got caching (and potentially token auth) for free.
- jensneuse 5y agoWhat you describe already exists. I'm the founder of https://wundergraph.com https://wundergraph.com and we're doing exactly what you describe, combining GraphQL with Auth and Caching, plus some more extras...
- orf 5y agoI was referring to deploying the graphql routers onto an AWS lambda within your own account, which looks entirely different from your product?
- tmitchel2 5y agoI totally agree. My startup uses graphql inside a lambda function. I'm not running at any scale yet but I just cant see the point of not leveraging all that autoscaling infra. Perhaps lambda at real scale costs more but I've not seen any data on that.
- orf 5y ago10 million executions with 1gb of memory at ~300ms per invocation costs like 40 dollars.