I wonder what made you guys go out and create graphql-yoga and prisma tooling around it? In the other examples referring to https://www.howtographql.com/ backend part You are using MVC frameworks like django and ruby on rails even Spring. in Node.js however there is a exiting MVC framework like sails.js but its not used here why?

Why Node doesn't have its version of Rails/Django/Phoenix etc is a topic that I'm not sure anyone can accurately answer. 🙂 Prisma came out of Graphcool's (GraphQL BaaS) data layer. And I think the motivation behind Yoga was to simplify Apollo Server config, but hopefully someone can speak more accurately to that.

This has been an concern of mine for while now. I consider this to be a stack graphql-yoga and prisma. People like my that don't know ruby or python not or little experienced with any MVC framework at all. This backend stack is all we got especially coming from JavaScript background(browser). What I mean about that is the great beginner-friendly docs. If know JavaScript much or little anyone can pick this stack up. However this whole eco-system is quite new and is that a good thing or bad thing. As young developer I cannot really tell whats bad and good

Building decoupled apps (view + API) is a big change for the server rendered guys. It's more work up front, but infinitely more flexible and faster when iterating and it's harder to corner yourself into the "ball of mud" so common in purely server rendered frameworks