exercises VS Hasura

GitHub: github.com/hasura/graphql-engine

A few years back, I decided to replace our spreadsheet-based host and service registries with a proper, Web-based asset registry. It took us a few days to hack together a simple system that we could use to track our infrastructure elements. It was not a big project -- just a simple app backed by a database, Hasura, and a React frontend. Since we were already using OpenID for authentication, it was easy for our team to start using it.

Hasura is a neck-to-neck competitor to Supabase as a BaaS, but with a crucial difference: its GraphQL-first approach. Unlike Supabase, Hasura doesn't bundle database services, allowing it to work with virtually any database including Supabase's own Postgres, Neon, and others.

Hasura and PostGraphile lead the PostgreSQL GraphQL landscape. Hasura provides real-time subscriptions and a powerful permissions system, while PostGraphile offers deep PostgreSQL integration and excellent performance for complex queries.

Here is an example data schema we get for a query using Hasura and GraphQL-Codegen

Hasura is a great tool. I was worried about a few things such as huge RAM consumption, excessive focus on new features and functions despite many outstanding issues, long time rewrite of the server in Rust, etc...

> 2. ORMs do not hide SQL nastiness.

This is certainly true!

I mean: ORMs are now well known to "make the easy queries slightly more easy, while making intermediate queries really hard and complex queries impossible".

I think the are of ORMs is over. It simply did not deliver.

If a book on SQL is --say-- 100 pages, a book on Hibernate is 400 pages. So much to learn just to make the easy queries slightly easier to type? Just not worth it.

I prefer jooq any day over ORMs. And dont get me started over what tools like Hasuna have to offer.

There are also some languages (forgot the names) that are SQL-done-right. Select in the back, more type safe, more logic, more in the same steps as the query gets executed. These need to be adopted by PG and MySQL and we're good to go. (IMHO)

https://www.jooq.org/

https://hasura.io/

[4] https://github.com/hasura/graphql-engine/blob/master/architecture/live-queries.md

Another strategy is to model access control declaratively and enforce it in the application layer. ZenStack (built above Prisma ORM) and Hasura are good examples of this approach. The following code shows how access policies are defined with ZenStack and how a secured CRUD API can be derived automatically.