Streamlines secure card data queries and has revealed performance limits that need improvement
What is our primary use case?
My main use case for Hasura is that my application is a GraphQL application, and since connecting to the database directly through my UI, Hasura gives very excellent access to directly reach the database and get the request back without any API or endpoint creation. With the same endpoint, we can get considerable data from the database directly.
A quick specific example of how I use Hasura in one of my applications is that our application shows the cards in the wallet, indicating how many points and gift cards the user has. When a user logs into our application and clicks on their gift cards, the UI makes a call directly to Hasura, where we calculate the particular user's details and collect the amount of the entire gift cards to return back to them. While doing that, we have several payment groups because a user can have different gift cards, for example Domino's or Amazon. While mixing them and providing the exact user those details, not allowing other users to access this user's specific details, Hasura is very helpful.
What is most valuable?
The best features Hasura offers are the permissions and the ability to connect to the database seamlessly when we use GraphQL, which Hasura handles exceptionally well.
These features impact my day-to-day work positively, as they are tremendously helpful at the application level architecture design. However, the disadvantage revolves around performance. You need to upgrade to the Enterprise version to achieve better performance and ensure proper memory is assigned in your hosting container for optimal speed as required.
Hasura impacts our organization positively by being extremely useful. When we create multiple actions and cache them with Hasura, the caching has proven to be more than helpful. Furthermore, integrating OpenTelemetry into our Node application with Hasura has the added benefit of tracking Hasura calls directly, which helps us monitor our performance effectively.
What needs improvement?
Hasura could be improved by enhancing the performance of the free tier version, particularly for small applications that can only accommodate around 500 MB. In my scenario, that would have made a noticeable difference.
What other advice do I have?
I have additional comments about my use case and how Hasura fits into my workflow, as it has been helpful in terms of managing permissions for each table and role so that only specific roles can access particular columns. Creating REST API endpoints for each permission management task in internal application admin UIs can be burdensome, but Hasura allows us to handle permissions efficiently. Additionally, if you are using the free tier version, it tends to be slow. I have not used the Enterprise version yet, but regarding the free tier, your application will only achieve more than 40 or 50 TPS at maximum, so that is something to keep in mind when considering Hasura.
When we implemented Hasura in our application, there was no prior framework, and we noticed significant advantages, especially given our need to manage numerous gift cards and user card details. Hasura simplifies making complex database queries that we would find difficult with our current relational database. Its features, including querying with parameters for equality, range checks, and uniqueness, lead to very fast results that the NodeJS application can handle easily.
I would rate Hasura overall as 6.5 to 7 for the free tier version since I have not used the Enterprise one. It is pretty basic and simple, with anything above five being adequate. Hasura simplifies implementing complex queries needed for my application, and its permissions allow one user's cards cannot be seen by another user. That is why I conclude it is excellent for permission-focused applications, but the concerns regarding the free tier performance limitations mean you cannot achieve over 100 TPS.
My advice for others looking into using Hasura is that if your application is not going to reach 50 TPS, then it is very good to use. I am rating Hasura overall as a 7 based on my experience with the free tier version.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Back-end data validation has become faster and clearer but complex workflows still need improvement
What is our primary use case?
My main use case for
Hasura is for back-end data validation.
A quick, specific example of how I use Hasura for back-end data validation is that we had an integration project from one tool to another tool to Epic and how that data is flowing. All data was integrated in Hasura database. From there I use the queries to fetch the data and find out how the data is integrated and how it is working.
About my main use case with Hasura, I felt Hasura is a pretty user-friendly tool.
What is most valuable?
The best features Hasura offers include the way I can construct my queries because I use it for back-end validation.
What I appreciate most about constructing queries in Hasura is that the entire process is beneficial because it was easy compared to other databases where I can go to the table and select the columns and drag it and construct the queries. The flexibility and the speed are exceptional.
Hasura has positively impacted my organization because for this project, whatever project I'm working on where previously we were using the normal DB2 and which was a little complicated to use, Hasura made it very easy to understand the data flowing and data integration.
What needs improvement?
I'm still using it, so I'm unsure how Hasura can be improved. Perhaps its framework and structure-wise aspects could be enhanced. I feel it's good overall.
Regarding needed improvements, many developers feel that the complex workflow and validations can be difficult to manage at scale, and debugging access issues are a little confusing. These aspects could be fixed.
For how long have I used the solution?
I've been working in my field for the last 17 years.
I have been using Hasura for about one to one and a half years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
I'm not understanding what it is, analytic application; is scaling I would say something along those lines?
How are customer service and support?
I have never tried to work with the customer support.
Which solution did I use previously and why did I switch?
Before using Hasura, we used to use SQL
DB2, and as I mentioned, it was pretty old and a little time-consuming. That's why we shifted to Hasura.
What was our ROI?
I have not seen a return on investment with Hasura because as a team member I used that one, and I'm not the best person to answer that. My manager would be better positioned to provide that information.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that I don't know about the cloud which one they used. About the licensing, I think the company provided it to us, so I don't know. The company worked on that one.
Which other solutions did I evaluate?
Before choosing Hasura, I am not certain. That decision was taken care of by our leadership team.
What other advice do I have?
Since switching to Hasura, I would say there are fewer errors because if we make any error, a detailed analysis will be shown and we can identify and correct it, saving more time on that.
My advice to others looking into using Hasura is that it's a good choice; performance-wise it is really good, so I would tell others that you can use it. There will be some challenges such as poor indexing and some inefficient GraphQL queries, but Hasura itself is really fast, so I would definitely suggest it. I would rate this review a 7.
Provides real-time error resolution but sometimes delays schema updates
What is our primary use case?
I have used MongoDB and MySQL, and for the last two years, I am using CockroachDB, which is better than these two. I have recommended it to two more of my colleagues who have also started working on CockroachDB, and they are building an application for the global market. They have started using CockroachDB because it has been very helpful.
I am using Hasura just for the GQL, GraphQL.
Hasura has connectivity with CockroachDB, and I am not directly calling CockroachDB, I am just calling Hasura. Internally, Hasura calls CockroachDB, gets the data, and populates it into our application. It serves as middleware.
We have real-time subscription in Hasura.
If I change anything in CockroachDB, it immediately impacts Hasura. For example, if I add new fields, it gets reflected in Hasura.
Integrating microservice architecture with Hasura provides an endpoint to incorporate into your microservices. It works as a connection string, and that's its main role.
What is most valuable?
Hasura's best feature is that it provides an API gateway, and it also provides remote schemas and monitoring, which are the best methods they are offering.
In the API playground, I can run my query dynamically; it has a GraphiQL integrated system. I can fix my error directly on this playground and then copy my query from it to my code.
Regarding security, Hasura provides API keys and secret keys. It is hosted there and offers these features, which are very good. I have role-based access; I can give four out of five team members access to the Hasura console and manage their access control according to their roles. If assigned as admin, they can do anything. Developers can run queries, and business developers can monitor metrics.
Hasura does not support custom business logic; it just provides Graph Query Language support to get the data. It offers an endpoint where I can fetch the data and create any endpoint, such as ABC, to get a desired output based on some input variables.
Hasura has event triggers, and I have used that feature. I find it effective to have these event triggers in my system.
The main benefits I see from using Hasura include being able to fix my queries on the playground in real-time rather than relying on Google or any AI solutions for error resolution.
What needs improvement?
One area I would like to see improved is that they are providing a cloud-based DB system, and aside from that, I don't have any additional requests.
For how long have I used the solution?
I have been working with Hasura for the last six months only.
What do I think about the stability of the solution?
I have no issues with stability or scalability; everything is good.
What do I think about the scalability of the solution?
I have no issues with stability or scalability; everything is good.
How are customer service and support?
The tech support was fine; they used to reply within one, two, or three days, and that is acceptable.
Which solution did I use previously and why did I switch?
Before Hasura, we did not have a chance to work on CockroachDB. We used DynamoDB, DocumentDB, and MongoDB from the AWS platform.
How was the initial setup?
The initial setup of Hasura was very easy. Once redirected to the dashboard, I can add a new project by clicking a button for a new project. It asks if I want to go with a free plan or a professional plan, and if I select the free plan, I provide a provider such as Google Cloud, Azure, or AWS. Based on this, I can create a new project and add my DB connection string, such as CockroachDB. Just put it in and click save to create the connection, after which I can launch the console.
What other advice do I have?
My advice for others considering Hasura is that sometimes it may not support capturing remote schemas effectively; for example, if I change something in CockroachDB, it sometimes fails to capture the change until one or two days later. I discussed this with the sales and technical teams, and they also recognized this issue. This can impact your business deadlines if it's not functioning properly.
Event triggers are required for situations such as creating backups every three or four days. For example, if I need to create an event that runs every three days for backups or integrates payment systems using webhooks such as Stripe, once Stripe updates the database, that data will be updated in my local database.
On a scale of one to ten, I rate Hasura a six out of ten.
Readymade graphql solution
What do you like best about the product?
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.
What do you dislike about the product?
Hasura should support Dynamo db as most of the tech companies now are using aws and their first choice is dynamodb.
What problems is the product solving and how is that benefiting you?
We already have a REST api in place which connects with the dynamodb at the backend. We wanted to expose the api as graphql as there are third party services which want to consume our api and they prefer the graph calls. To implement this we used hasura over the rest api to get our work done.
Grate opensource product for API integrations.
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Actually, we are looking for a product that provides very reliable, faster, and scalable performance for integration and deployment of APIS and Hasura fits the best for our requirements. so have chosen Hasura over many other products.
Hasura Fastest Graph QL
What do you like best about the product?
User Friendly Monitoring system and good speed, also excellent monitoring system
What do you dislike about the product?
If the user is a layman, he has spent time learning about it.
What problems is the product solving and how is that benefiting you?
Graph QL..used in research of e-commerece
Recommendations to others considering the product:
It is very good, can be used for current situation and trend
Having a wonderful experience with Hasura
What do you like best about the product?
In the Hasura Console, we can execute graphql queries but the intellisense that it provides for relations is time saving
What do you dislike about the product?
After some editing in data, we loose the current row, so need to find it again
What problems is the product solving and how is that benefiting you?
Connecting backend application with graphql using hasura client
Recommendations to others considering the product:
Hasura is best for learning and implementing graphql along with interacting with the database. I recommmed to try once
Works perfect out of the box
What do you like best about the product?
The tooling is great , the documentation is easy.
Go from 0 to production in seconds
What do you dislike about the product?
Nothing to dislike , saves lot of your time creating rest apis
What problems is the product solving and how is that benefiting you?
Real-time updates
Faster development time
Better migration and setup
Open auth
And I can list so many
Query support
Recommendations to others considering the product:
If you are getting started with hasura , it's very easy to setup on heroku. I loved this feature , we setup.and env for development in a day using this
Hasura created a graphl revolution
What do you like best about the product?
This product helps to incorporate graphql featues into exisiting postgres database
What do you dislike about the product?
It supports the Postgres database efficiently; others need attention from founders
What problems is the product solving and how is that benefiting you?
Instant graphql functional for an existing database
liked Hasura , it eased development
What do you like best about the product?
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!
What do you dislike about the product?
The permission UI looks a little bit confusing and no way to set multiple permissions at once
What problems is the product solving and how is that benefiting you?
It helped me create visualizing table relationship and foreign keys
Recommendations to others considering the product:
yes , Its a time saviour and lessen work loads when it comes to ERD of huge databases
