Top Rated Hasura Alternatives
It reduces developer effort to create basic crud apis, and it also beneficial for fixed cost type of project, it also reduces the client cost for backend guys. Review collected by and hosted on G2.com.
Using hasura there are lots of advantages, but personally I know only one disadvantage that new developers are forgetting the sql operation and complex query and it affects the logical ability of developers. Review collected by and hosted on G2.com.
25 out of 26 Total Reviews for Hasura
It is easy to use. It gives you immense power to connect with postgres database and run graphql query on it from step 1.
It also provides schemas which we can use in our code base to make graphql calls and mutation or subscription. Review collected by and hosted on G2.com.
Hasura should support Dynamo db as most of the tech companies now are using aws and their first choice is dynamodb. Review collected by and hosted on G2.com.
it is an open-source platform that allows you to integrate Graphql and REST API faster and reliably. when talking about the features it is a powerful query engine with the support of Dynamic access control. It is very easy to connect with schema using Hasura. we can use Hasura on the cloud and the local system so it supports both and which is very convenient for many users like me. What I like most about Hasura is when you connect it properly it automatically writes your queries and mutations in the console I think which is a very useful feature of this product. Review collected by and hosted on G2.com.
I do have not many disadvantages to this product but one point I want to add here is Hasura is a little bit tough for beginners like I had faced issues with connecting. Review collected by and hosted on G2.com.
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! Review collected by and hosted on G2.com.
Hasura automatically generates the GQL schema based on the SQL model, or does all the API job for us, and that's superb. But I think it's also Hasura's downside, being abstracting away this process leaves us with less control over out GQL API, so I think they can get better with that aspect (like optionally auto-generate an API depending on the dev team's decision. Review collected by and hosted on G2.com.
I like the GraphQL support and also Voyager. It really speeds up the development process by reducing the workload on the backend Team. Let's Team focus on Front-end development. Review collected by and hosted on G2.com.
Nothing as of now. I could say that I would love it if it can improve performance. Also, if we can have some Youtube Videos for tutorials. Review collected by and hosted on G2.com.
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 Review collected by and hosted on G2.com.
Hasura sure looks interesting, but two things make e hesitant:
1. The overly complicated schema it generates. For example, given an integer id, one can (and must) use various operators to query that id, e.g. `user(id: { _eq(1) })` rather than just `user(id: 1)`, where other operators are `_gt`, `_lt`, etc. To make this possible, hasura defines a comparison object, which results in a very long schema. However, often the only comparison that makes sense is equality, e.g. for IDs, so this should be optional.
2. More importantly, using Hasura establishes coupling between the DB and the GraphQL schemas. What if at a later stage one decides to remove information from the DB and move it to an external source? GraphQL was designed to hide such implementation details. With Hasura this is no longer possible. Review collected by and hosted on G2.com.
In the Hasura Console, we can execute graphql queries but the intellisense that it provides for relations is time saving Review collected by and hosted on G2.com.
After some editing in data, we loose the current row, so need to find it again Review collected by and hosted on G2.com.
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 Review collected by and hosted on G2.com.
Nothing found yet, but a small suggestion when resizing desktop to 2 windows, hasura lacks some what responsiveness. It will good to have tablet level responsiveness. Review collected by and hosted on G2.com.
when I learned how to use Hasura, I was able to create your GraphQL backends easier and faster than I ever thought possible without writing a single line of code! Review collected by and hosted on G2.com.
The permission UI looks a little bit confusing and no way to set multiple permissions at once Review collected by and hosted on G2.com.
