What advice do you have for others considering Hasura?

My advice would be to use Hasura when it provides the most value, such as when rapid API development and real-time data use cases are needed. My experience with Hasura was positive, and it has helped us accelerate development and reduce the effort around exposing and maintaining APIs. I would rate this review an 8.

One feature I have started trying out is Hasura Actions, which may not fit our project perfectly, but I think they are powerful. I would advise others considering using Hasura to have version control over their migrations because we do not have it, which I know goes against what Hasura proposes, and it is difficult. Updating anything related to the metadata, migrations, or Postgres tables is challenging because you have to tear everything down and bring it back up, and considerable time is lost. It is important to have that folder versioned. Custom SQL functions in Postgres are very useful for us because we were coming from a migration and needed to access data referenced in other tables. Those functions have worked well for us. I give Hasura an eight rating because at one point in the project it helped us move very fast. However, given our architecture, it is becoming a bottleneck because we are dealing with authorization topics and roles, and Hasura does not fit perfectly with our architecture. We may need to study a better way to implement it, but that is the current state of the project.

My experience while working with it was quite satisfactory. For others considering Hasura, its effectiveness varies depending on the company size and data amount. For medium-scale or startup companies, it is an excellent option since it is free, but it may not handle immense data for huge companies. I would rate Hasura as a seven out of ten based on my experience because it has some limitations, and I would have preferred more features, such as building complex queries, which are not possible in Hasura.

My advice to others looking into using Hasura is that if they have an automated system such as auto-renewal, or multiple source systems to deal with while using GraphQL, then I would suggest going with Hasura. I rate this product a 9.

I would give the advice that if others are looking to build something fast and want to avoid the overhead of writing boilerplate APIs and implementing RBAC, they can definitely go for Hasura because it saves a lot of time. I give this product a review rating of seven out of ten.

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.

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.

My advice to others looking into using Hasura is to look into it if you want to reduce your backend APIs, as that can be drastically reduced. Based on my experience so far, I do not think there are any other improvements that Hasura needs. I would rate this product an 8 out of 10.

Hasura is an overall good product. If you are using Node.js language, consider switching to Hasura. I would rate this product 8.5 out of 10.

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.