Graphcool / graphcool-framework

Apache License 2.0
1.77k stars 131 forks source link

Future of graphcool article #525

Open tsdexter opened 6 years ago

tsdexter commented 6 years ago

note: I would post this in the forum but it hasn't let me login for months now, I tried signing up with my github account today and it still won't login - just says "authentication complete: click here to continue" and takes me to unauthenticated forum homepage again

What feature are you missing? A blog post with the future of graphcool-framework

How could this feature look like in detail? Tradeoffs? Now that the company is funded and rebranding as prisma can we get some official guidance as to the future of graphcool-framework? Most importantly, if/when it is going to be mandatory to migrate to prisma as that could take significant time and resources for some production environments.

Also would be nice to get some guidance on whether or not the 467 existing issues will be worked on, especially ones like #489 which severely cripple any production environment in the case that it has to recover data.

Kisepro commented 6 years ago

For my part, I'm migrating to prisma. Rebranding to prisma, the lack of answers, the number of old bugs still not processed, no feedback, ...

I strongly hope to not make another bad choice with prisma and lose my time again !

DamianPereira commented 6 years ago

Would really love some communication too, I'm trying to use graphcool instead of prisma+graphql-yoga because I don't want a node server (graphcool is scala AFAIK), but there hasn't been any releases/commits to graphcool in a while, and prisma cli seems to be getting features not available on graphcool, like seed importing.

I read that the idea was to make prisma the query engine for graphcool, so graphcool becomes a wrapper around prisma which provides authentification and other server features.