Hasura raises $9.9M to simplify GraphQL
techcrunch.com
Hasura raises $9.9M to simplify GraphQL
1–10 of 199 posts
Re: Hasura raises $9.9M to simplify GraphQL
#2I tend to prefer PostgREST's[1] syntax over GraphQL for when I need flexible client-side queries. It's way more intuitive for me.
Re: Hasura raises $9.9M to simplify GraphQL
#3I often miss graphql features when working with rest APIs. But switching over seems very much not worth it when no one in the organisation knows graphql.
I feel like graphql would be much easier to adopt of it just sticked to rest conventions as much as possible. Like have the query language be pure JSON.
It should even be possible to design it so that you could make drop in replacements for most of existing rest APIs.
Re: Hasura raises $9.9M to simplify GraphQL
#4I often miss graphql features when working with rest APIs. But switching over seems very much not worth it when no one in the organisation knows graphql. I feel like graphql would be much easier to adopt of it just sticked to rest conventions as much as possible. Like have the query language be pure JSON. It should even be possible to design it so that you could make drop in replacements for most of existing rest API…
GraphQL is much easier to pickup and get productive than most people think, most of the times all you have to do is writing resolvers (functions) instead of http handlers (functions)
On the client side is the same, following any getting started guide can explain 90% of what you need to know in a single day
Re: Hasura raises $9.9M to simplify GraphQL
#5Hasura 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 put together: https://github.com/cpursley/react-admin-low-code
Re: Hasura raises $9.9M to simplify GraphQL
#6Hasura 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…
Wow I didn't know about React Admin, this is amazing.
Now I just need a way to migrate my data from somewhere else to Hasura.
Re: Hasura raises $9.9M to simplify GraphQL
#7While I like and enjoy many aspects of code generation such as this or Prisma, In real world scenario it just doesn’t feel right.
Imagine a very simple scenario, you want to add some validation based on business requirements, in order to do that you have to have a server with custom endpoints or a custom graphql server (thus copy most of what hasura generates) to implement your own validation
The only situation in which I consider this a really good solution is in a CQRS system where the database attached to hasura is read only via graphql and the data is inserted by other services making it a typesafe single source of truth to read from
Re: Hasura raises $9.9M to simplify GraphQL
#8While I like and enjoy many aspects of code generation such as this or Prisma, In real world scenario it just doesn’t feel right. Imagine a very simple scenario, you want to add some validation based on business requirements, in order to do that you have to have a server with custom endpoints or a custom graphql server (thus copy most of what hasura generates) to implement your own validation The only situation in wh…
Exactly! It could be useful for simple apps if they add a way to create basic validation rules with regex.
Re: Hasura raises $9.9M to simplify GraphQL
#9While I like and enjoy many aspects of code generation such as this or Prisma, In real world scenario it just doesn’t feel right. Imagine a very simple scenario, you want to add some validation based on business requirements, in order to do that you have to have a server with custom endpoints or a custom graphql server (thus copy most of what hasura generates) to implement your own validation The only situation in wh…
Often times that’s not needed if you actually use the full power of PG. CHECK constraints go a long way, and where they don‘t go, PG/PSQL goes pretty much a long way.
For internal or prototypical use cases, that can be totally sufficient, however you‘re right that you‘ll eventually want good error messages, observability and much more other custom logic.
What I‘m still searching for is something that works like Hasura or PostgREST and then offers „upgrades“, first via configuration, later via custom code hooks.
That would be pretty awesome from a migration path perspective.
Re: Hasura raises $9.9M to simplify GraphQL
#10Disclaimer: I work on MongoDB Stitch
This looks really cool and an improvement on Prisma! I particularly like the much less bloated schema experience (and the builder) along with the easy addition of actions. We've been working on something similar but it's great to see improvements in the UX of the space.