I work at Prisma and am involved with the Yoga 2 project. Sorry that our communication currently isn't very clear around this.

In general, Yoga 2 is still work in progress and we have a couple of questions that we still need to figure out (e.g. related to proper patterns for authorization and testing). There also might still be breaking changes in the future. However, it is certainly in a usable state and we would love getting some feedback on it already, so feel free to jump on it and share your thoughts with us!

Also, while Yoga 2 itself is still WIP, the underlying primitives from GraphQL Nexus and nexus-prisma are production-ready, so if you're a bit hesitant with using Yoga 2, you can still resort to building your server just based on nexus-prisma and get many of the benefits you get with Yoga 2.

Interesting post. I've been using type-graphql which kind of solve some SDL problems although I'm excited to try GraphQL Nexus.

This is a great discussion, thanks a lot for initiating it! I work at Prisma and want to point out a few things:

• What we're building with Prisma ultimately is more than an ORM. The idea to build an open-source version of the "data layers" that are used in the architectures of major companies like Facebook, Twitter, LinkedIn, ...

• Prisma currently requires running an extra server (typically using Docker). This is a limitation that will be lifted very soon.

• As opposed to traditional ORMs, we actually aim not only to make database access easier, but actually want to simplify many more database workflows:

  • Visual data management using Prisma Admin (this will replace any custom data dashboards that are often build per project)

  • Database migrations, we're currently working on an extremely powerful migration system. You can learn more about it here.

  • Query analytics to identify performance bottlenecks in your database queries.