I am so excited about Prisma, I have been lucky enough to follow Graphcool for almost a year. I am sure with all the experience Graphcool team had hosting a Graphcool BaaS, prisma is a take on the harder problems in GraphQL ecosystem. From an initial look at the docs, I can see that prisma is language and database agnostic (with the help of connectors) and it has built in support for subscriptions (and more). I have a few questions about the service though:

1. GraphQL specification does not have the spec for subscriptions yet, moreover, even when added I am sure where and how to manage the state of subscription will be an implementation detail. How close is the Prisma implementation to what can end up in the spec? What does the subscription implementation detail look like, how is the state stored? I noticed from docs “Because Prisma is a standalone process, it can be scaled independently from your application layer and provide scalable subscriptions infrastructure.” Can we elaborate on where prisma sits in the stack?

2. Is prisma language agnostic? How easy it is to add new languages?

3. Is prisma DB agnostic. Can it be connected to an existing database or REST service.

I think questions 2,3 boil down to “How is prisma different from a GraphQL application server like graphql-yoga with GraphQL binding”

Awesome to see Graphcool team coming up with solutions to build a flexible and scalable GraphQL infrastructure.