Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Enjoying Using hasura
What do you like best about the product?
Voyager support and easy to edit rows with ui
What do you dislike about the product?
It should have multi tab functionality for tables
What problems is the product solving and how is that benefiting you?
Event triggers are easily visualized
Recommendations to others considering the product:
Highly recommneded
- Leave a Comment |
- Mark review as helpful
Hasura, Best tool for speeding up the development process.
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Basically, I am a Project Lead. I look around for solutions that help speed up the delivery without ruining the quality. I have found that Hasura can be used for the backend without having to actually write code.
Hasura makes things easy
What do you like best about the product?
Explorer, voyager and even SQL support i like most
What do you dislike about the product?
sometimes increased load time for SQL queries
What problems is the product solving and how is that benefiting you?
Graphql queries easily formed, database visualization and table maintenance
Recommendations to others considering the product:
It will help you if you are new to the relational Postgres database definitely
A very nice product which I used for 1 year. Quickly start a new project.
What do you like best about the product?
quickly generate graphql schema from db schema. And provide ACL, AUTH, scription function to use.
What do you dislike about the product?
If hasura supports arm build will be cool.
What problems is the product solving and how is that benefiting you?
A subsciption to get real db data.
Awesome developer experience on adding a modern solution to a traditional RDMS.
What do you like best about the product?
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!
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!
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
I like building GQL API's but I often do that with a Graph API like D-graph and sometimes uses FaunaDB. Being on the JAMstack revolution, GraphQL is a big part of web developement, and the fact that Hasura brings the SQL based DB's in the innovation of web development makes it a bridge that connects SQL with the future. Building GQL api with a Postgres DB is now easier and it's fast.
Easy and user friendly interface that provides fast graphql query generation
What do you like best about the product?
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
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
I have worked on a real-time projects using hasura, as of now I found everything beneficial, because if it's user friendlyness
PrimeNG provide rich GUI features.
What do you like best about the product?
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
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
What do you dislike about the product?
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.
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.
What problems is the product solving and how is that benefiting you?
using this lib I almost saved lots of time
Recommendations to others considering the product:
I haven’t implemented anything using RLS. It just seemed the way to go since it’s native Postgres. The Hasura team gave me the same explanation as they give in this article - when you use RLS, you have to rerun every query for every client to get your results. By doing it in the application layer, you can run a single query instead.
Happy With Hasura
What do you like best about the product?
Voyager support with Hasura that let me generate erd easily
What do you dislike about the product?
no separate tab for opening multiple tables
What problems is the product solving and how is that benefiting you?
ERD diagram problems and visualizing table structure and creating new tables easily
Recommendations to others considering the product:
Sure to recommend, its usefull indeed
Wonderful tool to use to ease up your development
What do you like best about the product?
It was easy to handle data and integrate it with the frontend without even having a backend
What do you dislike about the product?
Nothing much, it was a great experience.
What problems is the product solving and how is that benefiting you?
We have been working on a event scheduler and we were able to do that without having to implement a lot in our backend
All you need to create a realtime backend
What do you like best about the product?
Hasura provides real-time graphql subscriptions with a data loader, so it's super fast.
What do you dislike about the product?
When you need to have a dedicated server with custom deployment, the migration and synchronization can be really painful.
What problems is the product solving and how is that benefiting you?
Web realtime web application
showing 11 - 20