Hi! We're starting a new (production ready in <...
# prisma-whats-new
p
Hi! We're starting a new (production ready in < 3 months) project. And we are looking forward to use graphcool 1.0. 😄 It seems like this has been renamed to prisma, should we go for graphcool 0.11 or prisma?
m
I think people on may need more info before they can answer a question like that
p
I'm trying to find the differences between the two. It seems like prisma is the graphcool 1.0 version? If so, will there even be a graphcool 1.0 or is it prisma from now on?
n
@patrick_madx please read this: https://www.graph.cool/forum/t/graphcool-framework-and-prisma/2237?u=nilan Let me know if you have any other questions 🙂
p
Perfect, thnx!
It's such a difficult choice!!!! 😛 continue with graphcool framework or prisma! Will graphcool framework still get a 1.0 version? Your primary focus will be on prisma right?
j
I’m trying to get an answer on this exact question as well…
p
Well I do get a lot of answers already by starting a graphcool-framework project and a prisma project (graphcool init vs prisma init). The clear separation between the database and the API is a good thing! However, we probably dont need such a seperation (for now), so the only reason to use prisma right away is when the graphcool-framework will stay behind in development.
m
Prisma is way more flexible than framework. I have learnt Prisma and using framework seems almost wrong now. I say you give it a shot, majority of concepts can be reused in framework anyway! 🙂
p
I decided to have a quickstart with graphcool framework and switch to Prisma once we get the datamodel right. We need a lot of server side functionality (cron jobs / emails / fine grained auth) so running our own graphql server is the preferred option.
Thnx @nilan @matic !