| > As engineer #2 it's a mess As a long-time Hasura stan, I can't agree with this in any way. > Your entire schema is exposed In what sense? All queries to the DB go thru Hasura's API, there is no direct DB access. Roles are incredibly easy to set up and limit access on. Auth is easy to configure. If you're really upset about this direct access, you can just hide the GQL endpoint and put REST endpoints that execute GQL queries in front of Hasura. > Business logic gets pushed into your front end because where else do you run it unless you make an API wrapper > Likewise you can't easily customize your API without building an API on top of your API. You're doing weird extra network hops ... How is an API that queries Hasura via GQL any different than an API that queries PG via SQL? Put your business logic in an API. Separating direct data access from API endpoints is a long-since solved problem. Colocating Hasura and PG or Hasura and your API makes these network hops trivial. Since Hasura also manages roles and access control, these "extra hops" are big value adds. > You're pushed into fake open source where you can't always run the software independently ... Are you implying they will scrub the internet of their docker images? I always self-host Hasura. Have for years. > I think the people who write this off as "backend engineers feel threatened" aren't taking the time to understand the arguments they're hearing I think your arguments pretty much sum up why people think it's just about backend engineers feeling threatened - your sole point with any merit is that there's one extra network leg, but in a microservices world that's generally completely inconsequential. |