Live data from Hacker News

Hasura raises $9.9M to simplify GraphQL

techcrunch.com

121–130 of 199 posts

Re: Hasura raises $9.9M to simplify GraphQL

#121
post #75
post #56

Earlier quoted context omitted.

There are so many good reasons to use it that I think I don’t make it justice. But here a few pros of graphile: - it is made in typescript and can be integrated as a library directly in a JS project - it is very easy to extend with plugins - it is very easy to customize and run on an existing database - it is « database first » in the sense that the schema is created based on the DB schema and some additional annotat…

I don't have any horse in the race but other than the "it is made in Node" everything else applies to Hasura (except the VC thing obviously). Do you have any other point to sustain this comment of yours? > my conclusion is that PostGraphile is way ahead of all this

I mean:

- Like Hasura, has ALL the features of Hasura

- BUT really FOSS with no VC funding, supported through Patreon by a super nice team.

- AND I have all the source, in the same language than the rest of my stack, the language that my developers know

- AND it does not require to run yet-another-microservice but is just part of my graphQL server

- AND it is extensible through plugins that blend seamlessly in the server (unlike Hasura where I see no sign of plugins, and I don't want to write plugins in Haskell)

- AND it supports native, super-fast Postgres Row-Level-Security instead of rolling their own!

That is very clearly compelling enough to support my conclusion, from my point of view.

Let me also mention that I have been burnt by another VC-funded GraphQL server company, namely Prisma, which left us stuck with an old, non-maintained buggy version which is near impossible to patch and build ourselves, while they work on their pie-in-the sky Prisma v2 which is totally the wrong direction in my opinion.

We jumped ship from prisma, considered hasura, but went for graphile and love it!

Re: Hasura raises $9.9M to simplify GraphQL

#122
post #116
post #113

Earlier quoted context omitted.

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

I'm reading through the docs now. They are pretty good! I assume I could just use say Apollo on the client? Maybe that part of the docs could use some additional info.

You are correct. You can use any GraphQL Client. Hasura has done an awesome job with tutorials here that you should look at:

https://hasura.io/learn/

Re: Hasura raises $9.9M to simplify GraphQL

#123
post #5

Hasura is a game-changer. I'm never writing CRUD backend apps again by hand. Combine Hasura (automatic GraphQL on top of PostgreSQL) with React Admin (low code CRUD apps) and you can build an entire back office admin suite or form app (API endpoints and admin front end) in a matter of hours. This adaptor connects react-admin with Hasura: https://github.com/Steams/ra-data-hasura-graphql Here's a reference application…

Tangentially related: As a side project, I've been building a backen-as-a-servive platform with a GQL interface derived from the data model and business logic.

Posting here as it may be of interest to readers: l https://massiveinference.com

Re: Hasura raises $9.9M to simplify GraphQL

#124
post #122
post #116

Earlier quoted context omitted.

I'm reading through the docs now. They are pretty good! I assume I could just use say Apollo on the client? Maybe that part of the docs could use some additional info.

You are correct. You can use any GraphQL Client. Hasura has done an awesome job with tutorials here that you should look at: https://hasura.io/learn/

Ah that makes sense, didn't even think to look there. Awesome, thanks for the help!

Re: Hasura raises $9.9M to simplify GraphQL

#125
post #75

Earlier quoted context omitted.

I don't have any horse in the race but other than the "it is made in Node" everything else applies to Hasura (except the VC thing obviously). Do you have any other point to sustain this comment of yours? > my conclusion is that PostGraphile is way ahead of all this

I mean: - Like Hasura, has ALL the features of Hasura - BUT really FOSS with no VC funding, supported through Patreon by a super nice team. - AND I have all the source, in the same language than the rest of my stack, the language that my developers know - AND it does not require to run yet-another-microservice but is just part of my graphQL server - AND it is extensible through plugins that blend seamlessly in the se…

Reading this makes me so glad I picked Postgraphile.

Re: Hasura raises $9.9M to simplify GraphQL

#126
post #48
post #5

Hasura is a game-changer. I'm never writing CRUD backend apps again by hand. Combine Hasura (automatic GraphQL on top of PostgreSQL) with React Admin (low code CRUD apps) and you can build an entire back office admin suite or form app (API endpoints and admin front end) in a matter of hours. This adaptor connects react-admin with Hasura: https://github.com/Steams/ra-data-hasura-graphql Here's a reference application…

Part of what I'm doing is working on a CRUD backend. The thing has a bunch of complex business and authorization rules. Not to mention a bunch of per-client customization. There's also some neat handling around versioning and copy-on-write type behavior to provide a mix of immutability and space saving. To me, this is CRUD because: most resources literally have 4 endpoints (create, index, update and delete). We write…

GraphQL by itself won't save you time, and might even increase it (it's a huge buy-in). You'd still have to implement the logic for those 4 endpoints, except now in a more complicated system.

In contrast, tools like Hasura and Postgraphile can potentially save you time because they generate the GraphQL part for you. Then you only need to handle the authN/authZ parts – in theory, at least.

Re: Hasura raises $9.9M to simplify GraphQL

#127
post #105

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.

FWIW, I went the other way, mostly because I found the GraphQL queries that I wrote in Hasura to be much nicer to read than the equivalents that I got with Postgraphile.

Yes, please say more. I've been idly looking that these both from a distance and I would not have expected differences along that dimension. I would expect the expose nearly identical GQL types from the same pg schema.

Re: Hasura raises $9.9M to simplify GraphQL

#128

A huge benefit that tools like Hasura, Postgraphile and PostgREST provide is using the native in-database row level security model. Consider Django. Your django app logs into the database typically as a user with elevated permission that is a superset of all permissions required by your users. Postgres has no idea that django is acting on behalf of many users, all it sees is this django super-like user. If an attacke…

+1 for Django

the Graphene implementation for Django brings up a Relay GraphQL server so fast. The best part is that at compile time it ensures your GraphQL schema confirms to the Relay standard, enforcing correct naming. You really don't have to think about much.

Re: Hasura raises $9.9M to simplify GraphQL

#129
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/

For rest apis on mysql instantly - https://github.com/o1lab/xmysql/

(shameless plug)

Re: Hasura raises $9.9M to simplify GraphQL

#130
post #5

Hasura is a game-changer. I'm never writing CRUD backend apps again by hand. Combine Hasura (automatic GraphQL on top of PostgreSQL) with React Admin (low code CRUD apps) and you can build an entire back office admin suite or form app (API endpoints and admin front end) in a matter of hours. This adaptor connects react-admin with Hasura: https://github.com/Steams/ra-data-hasura-graphql Here's a reference application…

I don't know. I have a feeling the minute you start having to write complex SQL-equivalent queries outside of SQL, you're in trouble.

I love Django, but even its amazing ORM has limitations. I can't imagine what it's like to deal with something similar but on the frontend instead...

Post reply on HN