What I like about Hasura is that you can easily use any of your SQL Database like Postgres into building a GraphQL API. Commonly, devs uses a graph database or maybe a document-oriented batabase to build graphql API, and it would be more work if the database is SQL, so the fact that Hasura exists is a huge relief. As a dev with a focus on the Front-end, GraphQL is really a game changer based on how easy it is to request data from the server. Unlike the traditional REST that takes us to many requests, GraphQL can do it once. That's why a GraphQL API is more attractive to Front-End. Now, since majority of the systems built out there are SQL based, it would be a huge hassle to migrate all those data to a more modern DB solution, and again, the dev community including me are so thankful to this awesome open source project for making the development experience more pleasant. And oh, I just forgot, Hasura is fast, like really fast, and that's a huge plus!

Can save time for creating backend DB, because hasura has built in functions that generates graphql over postgres. It also recommends various possible foreign keys and relations based on table Structure

Hasura saved the grunt effort of writing a CRUD and scalable real-time backend without interfering with how you’d write your business logic. It's easier to use rather than writing Postgres queries. Hasura is designed to be completely stateless and does not have a master-slave architecture. This makes it painless to scale Hasura: Vertical scaling: Increase CPU/RAM Horizontal scaling: Increase the number of replicas Auto-scaling: Setup up auto-scaling on your favorite container provider for automatic 1 to n scaling depending on traffic