prisma

Wow this is some really exciting news! I think it would be amazing to create a GraphQL API for FoundationDB. Therefore i have created a feature request for this in the Prisma repo. For those who don't know Prisma is a GraphQL database mapper for various databases. https://github.com/graphcool/prisma/issues/2240

>One weakness I've observed is that since each attribute of an object can make its own DB query, you can have a situation where a single GraphQL query can create dozens, or even hundreds, of individual DB queries, creating a performance issue with a naive implementation. This is mitigated with libraries that batch requests transparently, or with clever structuring of your schema that groups similar attributes into one query. From my experience writing a GraphQL server, I completely agree. This could really impact performance. I looked at multiple solutions including join-monster[0] and prisma [1] and settled on Prisma which I run on docker between my graphql server and my AWS RDS database. It translates queries into SQL for you :) [0]https://github.com/stems/join-monster [1]https://github.com/graphcool/prisma

This guide really only provides an overview of what GraphQL is so I think it's fair they don't go in depth about auth topics. If you're curios how authorization can be implemented in a GraphQL server, I recommend the following tutorial: https://www.prismagraphql.com/docs/tutorials/graphql-server-... Also check out these two awesome projects that provide ways for implementing authorization with GraphQL: - https://github.com/a-type/prisma-authorized - https://github.com/maticzav/graphql-shield If you want to see a practical example of how authorization can be implemented, check out this example project: https://github.com/graphcool/prisma/tree/master/examples/per...