Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hasura raises $9.9M to simplify GraphQL

techcrunch.com

Post reply on HN
Print view View original

171–180 of 199 posts

Re: Hasura raises $9.9M to simplify GraphQL

#171

Post by tango12 »

btilly wrote: post #167
markhalonen wrote: post #65

Earlier quoted context omitted.

I ultimately chose Postgraphile over Hasura. Mostly because the Postgraphile codebase seemed way hackable, written in TS/JS with a plugin architecture. I've tried some Haskell and that's just a whole nother world I don't have time to learn. So far it's working great for me.

I made the same evaluation 2 months ago and came to the same decision. But in my case it was because my existing database is a fairly complicated beast with a lot of updating through stored procedures on views. Hasura wanted to have control of what is happening in the database and there was zero chance that it would agree with the existing triggers about what should happen or how it worked. (Example of an issue, Hasu…

> But in my case it was because my existing database is a fairly complicated beast with a lot of updating through stored procedures on views. Hasura wanted to have control of what is happening in the database and there was zero chance that it would agree with the existing triggers about what should happen or how it worked. (Example of an issue, Hasura wants to own the view and view structure so that it can make real time subscriptions work.)

Unless I’m grossly misunderstanding, none of that is correct in the slightest!

Hasura doesn’t assume _anything_ about your table or view structure. Hasura will never interfere with your existing stored procedures either. At most hasura will refuse to track some items in your schema because they don’t adhere to the GraphQL naming spec. But hasura doesn’t own and control tables/views/triggers at all!

I’m actually really confused and surprised because this sounds exactly like the opposite of what Hasura does and what it was designed for, ie work with existing databases instantly.

I’d love to understand this in more detail and see if there was actually an issue and what it was. It's an important thing for us to look into and fix and would deeply appreciate your notes! Is there someway i can reach you?

Re: Hasura raises $9.9M to simplify GraphQL

#172

Post by shivekkhurana »

markhalonen wrote: post #84
shivekkhurana wrote: post #81

I settled for Hasura in a prod app after trying Postgrest, Postgraphile and Strapi. I believe its a permanent addition to my stack. The main reason for me was RBAC. Converting db-to-api is not that hard but providing access control almost always requires some form of middlewares. Hasura does RBAC very well. Another feature that I haven't deployed but find useful is webhooks. You can trigger webhooks as your data chan…

What made you choose Hasura over Postgraphile? RBAC is a postgres feature, not sure if that would affect the decision?

With Hasura, you can create arbitrary roles (like admin, manager, etc) and restrict access to data on the basis of these roles.

These roles can be assigned to a frontend session by generating signed JWTs.

With Postgres RBAC, you'd need something to lift the roles to be consumed by the frontend. With Hasura it works out of the box.

Also, I did consider using Postgraphile, but it was easier to get started with Hasura, so I went ahead with it. I don't have enough info to make a comparison.

Re: Hasura raises $9.9M to simplify GraphQL

#173

Post by elitan »

lucasverra wrote: post #88
elitan wrote: post #36

Earlier quoted context omitted.

What I liked with Firebase was how easy and fast everything was. One-click create a new project and everything was ready to use. It's this developer experience I want to mimic with Nhost. By providing a managed backend with simple to use js-sdk ( https://github.com/nhost/nhost-js-sdk ).

I'm a web entrepreneur and for my project i've been using Parse server project (1) implementation by Back4app (2). For the non initiated, Parse server is a API server module for Node/Express + mongo + websocket and stuff you need to run a commercial app like auth, role management et all. We chose this because : 1.Open source (no vendor locking although now i'm sure if i had to move from b4a it would be a small PITA 2…

Yes! The main advantages for me with the Hasura/Nhost stack is:

1. SQL (Thanks PostgreSQL)

2. Instant realtime GraphQL (Thanks Hasura)

3. Zero vendor lock-in

Re: Hasura raises $9.9M to simplify GraphQL

#174

Post by elitan »

SkyPuncher wrote: post #141
elitan wrote: post #36

Earlier quoted context omitted.

What I liked with Firebase was how easy and fast everything was. One-click create a new project and everything was ready to use. It's this developer experience I want to mimic with Nhost. By providing a managed backend with simple to use js-sdk ( https://github.com/nhost/nhost-js-sdk ).

I had the opposite experience with Firebase. Amazing at first, but quickly fell apart when I had to implement any sort of meaningful business logic.

Yes I agree with you. With Hasura there are 3 main ways to handle business logic. We use the first one at Nhost and it's working (and scale) very well.

1. https://3factor.app/

2. Actions - https://hasura.io/docs/1.0/graphql/manual/actions/index.html

3. Remote Schema - https://hasura.nhost.io/console/remote-schemas/manage/schema...

I know Hasura is actively working on this exact issue and they just released Actions (second option) and I think we will start to see a standard/best practice approach to business logic soon.

Re: Hasura raises $9.9M to simplify GraphQL

#175

Post by elitan »

dvasdekis wrote: post #155
elitan wrote: post #22

This is fantastic to see. First time I tried out Hasura back in late 2018 I was AMAZED. After going through multiple different stacks such as MeteorJS, Firebase, building my own REST/GraphQL API etc. Nothing really felt right. That was until I found out about Hasura. I actually had to assemble a quick meetup at the co-working space I was on (true story) to show everybody this software. Hasura Tweet: https://twitter.c…

Early nhost user here! Elitan's platform is a great way to get started quickly with Hasura, and he was also fantastic with helping me out on some then-undocumented components. Always grateful when a developer takes time to do a 1:1 call. Thanks again!

Thank you soooo much for your kind words ️

Re: Hasura raises $9.9M to simplify GraphQL

#176

Post by elitan »

chris_st wrote: post #169
elitan wrote: post #113

Earlier quoted context omitted.

Happy to hear. Let me know if you got some advice for us to improve the product.

Hi elitan -- since you asked, let me throw out my two cents. I'm comparing you to Heroku, sorry if that's not your ideal comparison. I think you need some different price points; the $4/month is great to get started, but the $40/month with 15M just really pales in comparison with Heroku's $50/month for 64G... particularly when I compare it with your $139/month for 5G of database. Thanks for a great looking product, t…

Good point! We will evaluate our pricing next month and make it more competitive and attractive while at the same time keep the business healthy.

Re: Hasura raises $9.9M to simplify GraphQL

#177

Post by elitan »

rsp1984 wrote: post #147
elitan wrote: post #22

This is fantastic to see. First time I tried out Hasura back in late 2018 I was AMAZED. After going through multiple different stacks such as MeteorJS, Firebase, building my own REST/GraphQL API etc. Nothing really felt right. That was until I found out about Hasura. I actually had to assemble a quick meetup at the co-working space I was on (true story) to show everybody this software. Hasura Tweet: https://twitter.c…

Firebase user here. I love Firebase because it offers so many components that (usually) play well together: Databases, Authentication, Machine Learning, Storage, Crash Reporting, Analytics, Messaging etc. Which parts of Firebase is Nhost replacing?

Nhost provides: Database, API, Auth, Storage.

Next on the road map: Cloud Functions, Hosting, Crash Reporting.

We try to go from the core and outwards. Hope it makes sense.

Re: Hasura raises $9.9M to simplify GraphQL

#179

Post by brillout »

Instead of Hasura and GraphQL, you can use RPC and directly write SQL queries to retrieve and mutate data.

One way to think about this is that with RPC you remove the whole API layer and directly write SQL queries instead, while permissions are defined programmatically on a case-by-case basis. This is much simpler than Hasura!

For Node.js there is https://github.com/reframejs/wildcard-api.

For other backends you can implement JSON endpoints (https://github.com/reframejs/wildcard-api/blob/master/docs/b...)

While scaling to a large company, you progressively migrate from RPC to GraphQL (with or without Hasura).

Re: Hasura raises $9.9M to simplify GraphQL

#180

Post by brillout »

rojobuffalo wrote: post #104
awb wrote: post #53

Some major players in the "GraphQL in a box" space: https://www.graphile.org/postgraphile/ https://hasura.io/ https://www.prisma.io/ There are plenty of "REST API in a box" solutions as well: https://github.com/PostgREST/postgrest https://github.com/prest/prest https://resthapi.com/

I've been working on GraphQL services since 2015. I worked on the design of the precursor to postgraphile; it was called postgraphql. Hadn't heard of Hasura before today, but it looks interesting. The primary complaints I hear from others about GraphQL are observability and the learning curve for devs who are new to it. I think these projects add a lot of value with tools like the GraphQL playground (similar to Graph…

Curious to know what you think of the React + RPC (e.g. https://github.com/reframejs/wildcard-api) + PostgreSQL stack in comparison to React + Relay + GraphQL + PostgreSQL?

RPC tightly couples frontend and backend. Decoupling is usually only needed for (very) large applications; while getting there you migrate from RPC to GraphQL.

Post reply on HN