I don’t think mapping your DB is necessarily a disadvantage. It provides a lot of benefits in modern web- and mobile-development which is where you’d use somet

I don’t think mapping your DB is necessarily a disadvantage. It provides a lot of benefits in modern web- and mobile-development which is where you’d use something like GraphQL. JavaScript works better when it knows the DB schemes, not only is it more efficient for your developers but it’s also higher quality because it allows fewer fuckups. If you’re building your DB schemes anyway, you may as well take advantage of GraphQLs other features. And it’s in a familiar language, any web developer can do a GraphQL query, and it’ll be efficient too. I think most developers can do a SQL queries too, but not always efficient. You can get a long way by going to W3 or google and hacking your way through a query to get what you want. Our business analytics and our LEAN process people do it, but I’ve seen some real horrors build that way by people who knew SQL but not databases. Build what you want, but there is a reason GraphQL is popular.