If you point is to abstract all the CRUD/GraphQL application, Go isn’t needed. You can go with PostgREST or Postgraphile. Source: over 2 years ago

What do you mean locally? Hasura is OSS, and you can run it locally (you have autogenerated SQL statements) Here you can just use Nhost and its CLI; Alternatives are https://github.com/graphile/postgraphile or dgraph as you mentioned. Hasura is working on support for sqlite, so you may have some blockers there, you can also look into the Prisma engine which has GQL as an intermediate (for resolvers, for example). - Source: Hacker News / over 2 years ago

I've personally found Postgraphile to be fantastic. Nicer to use than Hasura and fully OSS: https://github.com/graphile/postgraphile/. - Source: Hacker News / almost 3 years ago

Hi all, this sounds very cool. How does pg_graphql compare to Postgraphile? https://github.com/graphile/postgraphile (besides I guess running in the DB with PLpgSQL instead of as a NodeJS server) Did you think about integrating Postgraphile with the Supabase ecosystem or have specific limitations with it? Thanks! - Source: Hacker News / about 3 years ago

If you’re open to learning Postgres, I’d recommend postgraphile (https://github.com/graphile/postgraphile). Been using it for the past 2.5 years and only have good things to say. Source: over 3 years ago

Built on JSON API standards, the OSF API is intuitive for anyone familiar with REST conventions. Once you learn its core patterns, you can quickly expand into project creation, user collaboration, and more—without constantly referencing documentation. The official OSF API docs provide everything needed to get started. - Source: dev.to / 9 days ago

Following established patterns reduces the learning curve for your API. Adopt conventions from JSON:API or Microsoft API Guidelines to provide consistent experiences. - Source: dev.to / about 1 month ago

I’ve used both GraphQL and REST in the past. From json:api to Relay, each approach for building APIs has its pros and cons. However, a constant challenge is choosing between code-first and schema-first approaches. - Source: dev.to / 6 months ago

There is a group of people who set out to standardize JSON responses into a single response style, either for returning single or multiple resources. You can take their style as a reference when designing their API to ensure uniformity of responses. - Source: dev.to / 12 months ago

The server seems to be using the popular JSON:API standard which is a great way to build APIs. But should we really use these data structures in the frontend? - Source: dev.to / 11 months ago