Can someone explain to me how this differs from Apollo? Is it that it has a tighter integration with the DB layer?
Hasura raises $9.9M to simplify GraphQL
71–80 of 199 posts
Re: Hasura raises $9.9M to simplify GraphQL
#72Congrats to the Hasura team! Hasura is truly a marvelous piece of software when it comes to rapidly prototyping and getting things out into production. We discovered Hasura a couple years back at my previous company when it was still in beta and we were amazed with how easily we could automate most of our CRUD logic. I will definitely be using Hasura again when the time comes around. On a more recent note, I currentl…
We used appsync at my company and switched to a more classical approach of handwritten crud, a REST Api, a RDS (not entirely sure how well you can use them with appsync) away from dynamodb. Appsync was just not mature enough, had bugs and severe limitations. Without someone in the team who really knows Appsync, I would recommend against it and towards the tech you know.
Re: Hasura raises $9.9M to simplify GraphQL
#73If GraphQL needs $9.9M to be simple enough for developers to actually use it, why was it invented?
GraphQL definitely has its warts, but it provides more flexibility on the API response than you'd get with ReST, so you're neither sending the whole world to keep your API space small nor adding new endpoints to handle each new client use case. But, GraphQL doesn't fundamentally change the fact that something needs to be responsible for enforcing access restrictions and talking to a database. Hasura is working to sim…
>GraphQL doesn't fundamentally change the fact that something needs to be responsible for enforcing access restrictions and talking to a database.
This is what I'm struggling with when it comes to weighing the pros and cons of GraphQL. I like the SQL model, ie pushing selects and joins and such to the DB, so why not from client to host too? But when you still need to enforce access restriction and such per user per action, how much time would it save me, really?
Seems great for internal apis or prototyping though.
Re: Hasura raises $9.9M to simplify GraphQL
#74Awesome to see the GraphQL community growing, there's a GraphQL Landscape of tools out there, if something is missing please contribute, the GraphQL Foundation is tracking everything now: https://landscape.graphql.org/
Re: Hasura raises $9.9M to simplify GraphQL
#75Earlier quoted context omitted.
Can you elaborate?
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
Re: Hasura raises $9.9M to simplify GraphQL
#76I'm curious if anyone here has compared Postgraphile to Hasura? My personal difficulty in implementing these is that there aren't good source control and code organization tools for SQL and managing rollbacks and rollforwards in a sane way. (And a way that doesn't require writing rollbacks, which sometimes aren't even possible anyway).
I've done exactly that with a sample food delivery project. Same frontend, but two different backends (one with Hasura, one with Postgraphile).
Feel free to check it out: https://github.com/sastraxi/great-bear
Re: Hasura raises $9.9M to simplify GraphQL
#77Congrats to the Hasura team! Hasura is truly a marvelous piece of software when it comes to rapidly prototyping and getting things out into production. We discovered Hasura a couple years back at my previous company when it was still in beta and we were amazed with how easily we could automate most of our CRUD logic. I will definitely be using Hasura again when the time comes around. On a more recent note, I currentl…
We used appsync at my company and switched to a more classical approach of handwritten crud, a REST Api, a RDS (not entirely sure how well you can use them with appsync) away from dynamodb. Appsync was just not mature enough, had bugs and severe limitations. Without someone in the team who really knows Appsync, I would recommend against it and towards the tech you know.
What was the biggest hurdle you ended up facing that ended up being the dealbreaker for your team?
I think for us, the biggest issue so far has been figuring out some of the more involved Velocity templates as the documentation is fairly sparse and testing them can be a pain. Thankfully this project isn't too business logic heavy but due to time constraints, we ended up writing Lambdas for templates we could not figure out quickly.
Re: Hasura raises $9.9M to simplify GraphQL
#78Re: Hasura raises $9.9M to simplify GraphQL
#79Is it a good idea to base your GraphQL schema on your database schema? Isn't the point of GraphQL to decouple your interface (who should not break) from your backend implementation details?
You would never expose your database directly to the whole world.
Either it is an internal service, only consumed by your own products, and then it's fine. Or you have an API gateway to control who and how your services are queried.
The API Gateway is your interface who should not break. Your services communicating with your database (through Prisma, Hasura, any ORM, ...) can and will break.
When you base your GraphQL schema on your database schema for your internal services, you get rid of one long and annoying step of putting glue everywhere. This is especially true in a microservice architecture, and even more in the corporate world where you are expected to produce code quickly.
Re: Hasura raises $9.9M to simplify GraphQL
#80Firebase, React and Hasura let me set up new app ideas in like negative time. Hasura is especially amazing because of it's authentication handling and migration management.