REST vs GraphQL for Postgres: open‑source API generators and the API surface of SQL

REST is getting an open-source upgrade for PostgreSQL, and the debate with GraphQL just got more tangible. The Open-Source Postgres API Generator from QueryDeck turns a Postgres database into a production-ready REST API in minutes, with a GUI for deep joins and nested inserts. It prints out REST endpoints that work with your existing schema, and can deploy as a cloud REST API or export a NodeJS app. It’s open source under Apache 2.0 and even hints at future support for MySQL and SQL Server. ^[1]

PostgreSQL 18 is shipping more performance and polish, not just new toys. The release highlights include parallel builds for GIN indexes, cutting rebuild times and headaches for large indexes. That’s a practical boost for teams juggling big schemas and complex queries. ^[2]

The wider ecosystem chatter includes OrioleDB work from the Supabase crew—aiming for GA later this year or early next year and patches that could feed into upstream PostgreSQL, including TAM-related updates. It underscores a vibe where REST-first generation tools sit alongside deeper storage-engine experiments, all maturing as PostgreSQL 18 refines the core. ^[2]

What this means for adoption: REST-first API generators make exposing Postgres data with complex relationships easier without diving into GraphQL boilerplate, while PostgreSQL 18 brings performance and compatibility improvements that reduce the pain of bigger deployments. The combination nudges teams toward practical REST surfaces, backed by a healthier, more capable Postgres ecosystem. ^[1][2]

References