Using Supergraph a GraphQL to SQL compiler to quickly build apps on Postgres
In 2015, Facebook introduced GraphQL, a front-end query framework designed to shield users from the intricacies of the various backends one would find in modern data stacks. As with ORMs before then, most backend code ended up being databases, adding layers of abstraction that ended up being inefficient and required immense investments to scale out for performance. Additionally most app developers are not very familiar with SQL and go to great lengths to avoid learning it. This has created several problems like n+1 queries, inefficient queries, minimal use of database features, etc. While Postgres is growing in popularity with this audience the large majority of advanced features like JSON support, Recursive CTE’s, Window functions are never used. Often developers are unfamiliar with even simple features like the various types of JOINS and choose inefficient solutions like multiple queries instead.
In 2015, Facebook introduced GraphQL, a front-end query framework designed to shield users from the intricacies of the various backends one would find in modern data stacks. As with ORMs before then, most backend code ended up being databases, adding layers of abstraction that ended up being inefficient and required immense investments to scale out for performance. Additionally most app developers are not very familiar with SQL and go to great lengths to avoid learning it. This has created several problems like n+1 queries, inefficient queries, minimal use of database features, etc. While Postgres is growing in popularity with this audience the large majority of advanced features like JSON support, Recursive CTE’s, Window functions are never used. Often developers are unfamiliar with even simple features like the various types of JOINS and choose inefficient solutions like multiple queries instead.