I wrote up some thoughts today on GraphQL+Lambda in production https://gist.github.com/southpolesteve/08edb6a481c07f66eb71e4df619827ae …https://twitter.com/JoeEmison/status/916665531788341248 …
Yep! Mostly. I have some ideas about how to do pagination better but haven't implemented them yet.
-
-
I would also recommend the graphql-tools package. Keeping schemas in strings and separate from resolvers is
It didn't work for us when I wrote this but bustle has since adopted it. -
Would also just recommend doing auth in the resolvers. Not sure it's worth it to hack into the graphl schema. Maybe directives. *Maybe*
End of conversation
New conversation -
-
-
Did you use DynamoDB? I gotta say, I am sort of terrified because I feel like I need an advanced degree to understand the docs/language, and I am not sure I understand all of the strengths/weaknesses and don't want to shoot myself in the foot.
-
I have used (and migrated off) dynamo DB many times. It is good at specific things and has very sharp edges. Not sure I can fit all my dynamo thoughts in a tweet. Dyanmo is best when you know your query patterns up front.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.