3 ms·
Hasura puts an GraphQL interface on top of my PG. It adds authorization, has plug in based authentication, comes with a decent SQL schema editor, has some migra
by cies 6y ago
Hasura puts an GraphQL interface on top of my PG. It adds authorization, has plug in based authentication, comes with a decent SQL schema editor, has some migration system built in, and can serve as a proxy to other services. Use hasura-backend-plus and authentication (including email verification, forgot password, etc.) all just works.
Then I generate my client code from the GraphQL schema. I like strong typing so I use Elm on the front end. Now I have strong typing from SQL table to frontend code.
This is a game changer! I dont even want stringly typed SQL, not in the backend not in the front end. I want strong types guarding me against my own stupidity.
- atom_arranger 6y agoPeople interested in this can also checkout Postgraphile. I’ve been using both the past few weeks and have preferred Postgraphile.
- cies 6y agoCould you explain what you preferred in Postgraphile?
- atom_arranger 6y agoI've tried building the exact same app using Hasura and Postgraphile after having built another app in Postgraphile: - Postgraphile has better Relay support, stuff like returning added edges, returning deleted nodes, good global ID support. - Hasura didn't support something like adding a currentUser field when using the Relay support. The pagination in the non-Relay mode was very basic and didn't comply with the Relay pagination spec. - Comparatively even when not using Postgraphile's Relay support it still supports both the Relay pagination API and the easy "nodes" pagination API. - With Hasura I initially liked the UI for management but found it tedious as I continued working. - I came across some bugs with Hasura's pagination API's, which was the final thing that made me decide to switch to Postgraphile.