Dear @meep and @Noah_Davis, thank you for your clear thoughts.
As an aside. Netlify looks interesting
They are really incredible, love them.
As my graphql queries grew more complex, I was having to process and format much of the data on the client-side.
Yes i would have used a Gateway in front of it. But then again this is was Prisma + Yoga is supposed to do actually.
As time went on my interface and data models grew in complexity. I think that the graphcool team have realized the limitations of the current framework and the need to separate out server api from the db graphql api. Hence why the future is prisma. …
Yes, exactly my thoughts. That’s why i’m really craving for Prisma.
But you guys really made me rethink it… It feels bad and kind of dirty again to build on outdated product version and start a project with technical debt. In about 8 months from now, we would have to migrate back to Prisma in anyway.
This is what i actually would like to do. I do have a time horizon of 2-3 months until i need something ready for prod. We also would like to use it with Aurora RDS.
By the way: @nilan has already confirmed that this will work, so i’m really confident on that part.
So, if a friend asked me, will Prisma be ready for prod in 2-3 months, i would say: I desperately hope so - but please ask @nilan.