4 ms·

Can someone compare to Hasura please? What has been your experience?

terrortrain 5y ago
I came here with the same question. Hasura is really awesome, so far as I have used it. Now I gotta look into prisma I almost wonder if they aren't mutually exclusive. With hasura, you need to run your own server anyways, for auth or special cases. Maybe that server could run prisma? Let hasura do the migrations, and prisma track it?
nwienert 5y ago
I use Hasura and generally like it, it certainly has some sharp edges, but overall has worked. I think Hasura has much richer GraphQL support, which I pair with gqless[0] to get what I think is a much nicer client side / ORM experience overall. Other upsides are a much better RBAC column/row permissions, migrations with up/down, a better admin UI. [0] https://gqless.com https://gqless.com
- sbacic 5y ago
  What sharp edges are you referring to? I find that with new tech, I'm more interested in what it can't do rather than what it can.
  - nwienert 5y ago
    Hard to remember them all now, but definitely had a number of bugs I've ran into, most able to be worked around. For example a recent one was a huge slowdown in a simple query that should be optimized[0], still have no great solution for it or attached to any roadmap. One big one is at some point you need caching on a query level, and for that you have to purchase enterprise. I suppose they need to make money somehow, and it's a smart level to do it because it's almost impossible to not need caching at some fairly early stage. It would be nice if they let you test it out without "Contact Sales", and while there may be some way to wrap it from above, I don't think it's very easy. A meta critique would be the project seems to have less momentum than Prisma. Releases aren't as frequent or large, and I'd have much preferred they double down on PG and keep adding query abilities, performance, etc, instead of expanding database engines. [0] https://github.com/hasura/graphql-engine/issues/5745 https://github.com/hasura/graphql-engine/issues/5745
    - sbacic 5y ago
      Yikes! That sounds like it has "vendor lock-in" written all over it.
      - nwienert 5y ago
        Yea, but it’s a lot better than what’s out there, as far as I know, even with Postgraphile having progressed a lot.. and it is open source.

I came here with the same question. Hasura is really awesome, so far as I have used it. Now I gotta look into prisma I almost wonder if they aren't mutually exclusive. With hasura, you need to run your own server anyways, for auth or special cases. Maybe that server could run prisma? Let hasura do the migrations, and prisma track it?

nwienert 5y ago

I use Hasura and generally like it, it certainly has some sharp edges, but overall has worked. I think Hasura has much richer GraphQL support, which I pair with gqless[0] to get what I think is a much nicer client side / ORM experience overall. Other upsides are a much better RBAC column/row permissions, migrations with up/down, a better admin UI. [0] https://gqless.com https://gqless.com

sbacic 5y ago
What sharp edges are you referring to? I find that with new tech, I'm more interested in what it can't do rather than what it can.
- nwienert 5y ago
  Hard to remember them all now, but definitely had a number of bugs I've ran into, most able to be worked around. For example a recent one was a huge slowdown in a simple query that should be optimized[0], still have no great solution for it or attached to any roadmap. One big one is at some point you need caching on a query level, and for that you have to purchase enterprise. I suppose they need to make money somehow, and it's a smart level to do it because it's almost impossible to not need caching at some fairly early stage. It would be nice if they let you test it out without "Contact Sales", and while there may be some way to wrap it from above, I don't think it's very easy. A meta critique would be the project seems to have less momentum than Prisma. Releases aren't as frequent or large, and I'd have much preferred they double down on PG and keep adding query abilities, performance, etc, instead of expanding database engines. [0] https://github.com/hasura/graphql-engine/issues/5745 https://github.com/hasura/graphql-engine/issues/5745
  - sbacic 5y ago
    Yikes! That sounds like it has "vendor lock-in" written all over it.
    - nwienert 5y ago
      Yea, but it’s a lot better than what’s out there, as far as I know, even with Postgraphile having progressed a lot.. and it is open source.