“1. Hasura – GraphQL-first, with automatic APIs over PostgreSQL and other databases.”
“Hasura is probably the strongest option if your primary requirement is automatically exposing relational database data through GraphQL.”
“Automatically generates GraphQL schemas from database tables.”
“Supports relationships between tables.”
“Supports nested queries, filtering, sorting and pagination.”
“Supports GraphQL subscriptions.”
“Offers REST endpoints through configured RESTified queries and actions.”
“Supports data federation across databases and external APIs.”
“Hasura, for example, compiles GraphQL queries into optimized SQL operations.”
“2. Supabase – REST-first, with automatically generated GraphQL through pg_graphql.”
“If you want both REST and GraphQL without maintaining two separate backend implementations, Supabase is particularly attractive.”
“Automatically reflects your database schema.”
“Supports relationships derived from foreign keys.”
“Supports deeply nested queries.”
“Supports CRUD operations.”
“Uses PostgreSQL permissions and Row Level Security.”
“Supabase also has a particularly interesting REST implementation: PostgREST supports embedding related records.”
“Supabase also resolves its REST and GraphQL queries close to PostgreSQL.”
“4. Nhost – Provides a GraphQL-first backend powered by Hasura.”
“It is particularly interesting if you want a complete backend rather than just an API-generation layer.”
“You get automatic relational queries, mutations, permissions and subscriptions.”
“If you want authentication, storage, PostgreSQL and GraphQL packaged together, Nhost is worth evaluating.”
“3. Directus – Provides both REST and GraphQL APIs over your database.”
“5. AWS AppSync – Managed GraphQL API service with integrations for databases and other AWS services.”
“Its main advantage is that it can combine different data sources into one GraphQL API.”
“It is therefore more flexible but requires more API configuration.”
“However, unlike Hasura, it generally requires you to define schemas and configure resolvers connecting GraphQL fields to your data sources.”
“It is therefore more flexible but requires more API configuration.”
“6. Hygraph – GraphQL-native content backend, with a different focus from general-purpose database backends.”
“Native GraphQL queries and mutations.”
“Relationships between content models.”
“Filtering and pagination.”
“Content federation.”
“Remote REST and GraphQL data sources.”
“Its strength is querying related content and combining it with external data through a unified GraphQL API.”