Lessons learned from running GraphQL

Re:Lessons learned from running GraphQL by orf on Saturday September 25, 2021 @08:31AM (#28652620)

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.

[ Parent | on HN ]

Re:Lessons learned from running GraphQL by jensneuse on Saturday September 25, 2021 @09:09AM (#28652880)

What you describe already exists. I'm the founder of https://wundergraph.com and we're doing exactly what you describe, combining GraphQL with Auth and Caching, plus some more extras...

[ Parent | on HN ]

Re:Lessons learned from running GraphQL by orf on Saturday September 25, 2021 @09:17AM (#28652939)

I was referring to deploying the graphql routers onto an AWS lambda within your own account, which looks entirely different from your product?

[ Parent | on HN ]

Re:Lessons learned from running GraphQL by tmitchel2 on Saturday September 25, 2021 @09:43AM (#28653134)

I 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.

[ Parent | on HN ]

Re:Lessons learned from running GraphQL by orf on Saturday September 25, 2021 @09:51AM (#28653191)

10 million executions with 1gb of memory at ~300ms per invocation costs like 40 dollars.

[ Parent | on HN ]