by dikaiosune on 1/16/18, 5:17 PM with 9 comments
by divyenduz on 1/16/18, 6:14 PM
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.
by iamclaytonray on 1/16/18, 6:15 PM
I do wonder... Why does Prisma only support SQL? What's holding Prisma back from supporting NoSQL databases as well? I'd be very interested to hear why!
by hoodsy on 1/16/18, 5:26 PM
This isn't even to mention the inclusive, responsive, and engaging community. Whenever support is needed or there are questions to be answered, they are on top of it ASAP.
Came for the product, stayed for the team (and the product ).
by gentle-noah on 1/16/18, 6:17 PM
by mlukaszczyk on 1/16/18, 5:54 PM
What databases does it support?
Also love the name and logo. I see you at the dark side of my resolvers :v
by forsakenharmony on 1/16/18, 6:17 PM
What are the options for self hosting?