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

151–160 of 199 posts

Re: Hasura raises $9.9M to simplify GraphQL

#151

Post by pier25 »

crubier wrote: post #121
pier25 wrote: 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…

Don't get me wrong, I agree with most of your points as I'd prefer to work with Node than Haskell, but I still don't see how it is "way ahead" of the other options outside of personal preference.

Unless I'm missing something, Hasura is FOSS too.

https://github.com/hasura/graphql-engine

True, Hasura does not have plugins (AFAIK) but you can extend it's funcitonality via webhooks and PG views.

As for authorization it may give them more flexibility to roll their own.

Anyway, thanks for bringing up PostGraphile. I'll check it out!

Re: Hasura raises $9.9M to simplify GraphQL

#152

Post by Huggernaut »

rattray wrote: post #106
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've always been a huge fan of the Graphile (aka postgraphile) approach. It's just an open-source library, that you can run as a binary when you're just getting started. But when you start getting deep in production territory, it's extensively pluggable and you can gradually swap everything out for your own code, contribute/fork if you need (it's just TS), etc. Full control. I love the Hasura folks too, and they're a…

Benjie is legit awesome. We (storyscript) sponsor him and he's unbelievably valuable. I definitely abuse his time and he's always happy to help.

Re: Hasura raises $9.9M to simplify GraphQL

#153

Post by RussianCow »

michelpp wrote: post #145
RussianCow wrote: post #131

Earlier quoted context omitted.

> Django requires you to "meta-model" you have to write Python classes that map to your tables, this is usually duplicate work. You don't have to duplicate any work because you don't actually have to write any raw SQL, since it all gets translated by Django. So yes, there's an extra layer of abstraction there, but no duplication on the developer's part. > Django's ORM must support many databases, so it produces "leas…

> You don't have to duplicate any work because you don't actually have to write any raw SQL, since it all gets translated by Django. So yes, there's an extra layer of abstraction there, but no duplication on the developer's part. There is still some duplication of effort, for example when you change the model, yes django will create the migration script for you, but you always have to verify it and often change it es…

For the record, I do agree with your general sentiment that many of these abstraction layers are unnecessary, and in many ways harmful. Especially when it comes to data integrity, trying to enforce constraints and triggers at the application level is always going to be clunky and error prone, and monolithic frameworks like Django and Rails actively encourage you to do everything at their level and give you many ways to shoot yourself in the foot. But I also don't think Hasura and Postgraphile and related projects are the silver bullet. Why can't we have something in the middle? How about a web framework that leaves data integrity up to the DB and just gives you an easy way to "glue" together bits of logic and queries, and do migrations, etc? Or even just use Django/Rails/whatever but don't use the footgun features? At least then, if/when you do need to scale (in any sense of the word) past what a relational DB can offer you, you can easily do that instead of trying to shoehorn everything into the DB.

Aside: I'm working on a GraphQL library for Python that I hope will fulfill these goals, but development on it has stalled due to lack of time. Hopefully I can pick it up again soon.

FUD may have been strong, but in general I detest when people decry entire categories of technology as being "wrong" or unfit in an absolute sense (or, conversely, tout a technology as a silver bullet), when in fact everything has its tradeoffs and there are good reasons to use almost anything. Understanding those tradeoffs is vastly more important than searching for the universal answer to everything.

PS: Hope you're doing well! :) Your contact info isn't on HN, but email me if you want to get coffee/lunch sometime!

Re: Hasura raises $9.9M to simplify GraphQL

#154

Post by pyrale »

samblr wrote: post #134
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…

Just tried hasura, it is amazing to get all crud graphql apis out of box. How do we add business logic ? Folks @hasura, where do we learn about haskell ? any helpful pointers much appreciated.

You may enjoy the work done by Julie Moronuki and Chris Martin. They do lots of great learning stuff related to haskell.

Re: Hasura raises $9.9M to simplify GraphQL

#155

Post by dvasdekis »

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!

Re: Hasura raises $9.9M to simplify GraphQL

#156

Post by dvasdekis »

samblr wrote: post #134
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…

Just tried hasura, it is amazing to get all crud graphql apis out of box. How do we add business logic ? Folks @hasura, where do we learn about haskell ? any helpful pointers much appreciated.

I'm running a full production algorithmic trading platform, and our frontend interactions are handled by Hasura. For me, the appeal was in writing all the business logic as Postgresql triggers, which (provided they're written as true SQL and not plpgsql), scale beautifully with load. Hasura has a real appeal when you're keen to do your important logic in SQL.

Check out the result here: http://www.hedgecheap.com

Re: Hasura raises $9.9M to simplify GraphQL

#158

Post by dvasdekis »

cpursley wrote: post #33
jo-m wrote: post #17

Earlier quoted context omitted.

Looks cool! I cloned it and ran it locally. I noticed there was no backend running locally, and then saw it points to https://low-code-api.herokuapp.com/v1/graphql . Is the code running there available in a repo too? It would be super nice if you could link to it from the project README.

When I have a chance I'll refactor this so that it uses a local docker Hasura and Postgres instance.

+1 for this please! I am struggling with exactly this problem - how do I use React-Admin effectively on top of Hasura?

Would really appreciate it! :)

Re: Hasura raises $9.9M to simplify GraphQL

#159

Post by mongol »

MadWombat wrote: post #148
batmansmk wrote: post #111

Earlier quoted context omitted.

Data-driven architectures are very relevant, in particular in a corporate / business environment. I found all the answers in the docs. A SQL Schema can carry a custom query, it's called a view. A SQL Schema can carry a custom algorithm, it's called a function or a generated column. You can always deactivate permissions on a table to not expose it, my bet is that your backoffice will need to though. On top of that, Ha…

> A SQL Schema can carry a custom query, it's called a view. This is not feasible. I might not have enough access to create views. I might not have access to create functions. I cannot deactivate permissions if I only have a single access account and other systems use it already. You cannot assume that I have full control of the database or that I can easily make changes to the schema. But this is not all. I am worki…

Of course, if you don't have that access, it becomes harder and less suitable. BUT: If you have that ability, it is quite good. I think we are going into a SQL renaissance, especially if frameworks like this article is about will succeed in overcoming the classical ORM impedance mismatch

Re: Hasura raises $9.9M to simplify GraphQL

#160

Post by dpacmittal »

markhalonen wrote: post #89
deckard1 wrote: post #83

Earlier quoted context omitted.

GraphQL is mediocre. It's luke-warm mashed potatoes from a chain diner. Having used it for a number of years now, I still don't know why people recommend it beyond other people recommending it. Out of the box, it comes with no batteries included. Which explains the cottage industry that popped up to support it (Apollo, Hasura, etc.). Simply making GraphQL as efficient as bog-standard REST without involving the use of…

After using GraphQL with code-generated Typescript types on the response, I can't imagine going back to REST and it's "hope and pray" the JSON looks how you expect it to look

> After using GraphQL with code-generated Typescript types on the response

What library are you using to generate the types?

Post reply on HN