Is it possible to customize the graphql resolvers in order to implement some complex logic? That one thing is what scares me away from serverless solutions. I've tried AWS AppSync and it was a nightmare to have to deal with having to write custom AWS Lambda functions that would overwrite the default methods and work with velocity template stuff etc. I'm now working with a Django API with Graphene for the GraphQL part and I like how much control it gives me in designing stuff. Of course the disadvantage is that it is not as straightforward and effortless to set up as what we're looking at here, but it pays off in the long run in letting us do some complex stuff that might crop up later on.
But (completing all you guys have said), if you have another API with Express, or whatever, and you want to apply this code onto your app, Hasura let you to join that external API to the GraphQL basic API that has been built with it. It's ridiculously awesome.
Hello, does this also work with an existing project having mLab (cloud mongodb database) if I follow through this tutorial? Schemas, type definitions and resolvers are already defined in the server. So I want to migrate an existing app to docker and Hasura.
This is really helpfull man thanks
I love this video-- gives me chills seeing what is possible with this framework.
Thank you for such a precise, crisp and helpful video :)
This is mind blowingly Cool Thanks bro
Who codes in Times New Roman?
For some reason I find it better looking than some current fonts :/
Is it possible to customize the graphql resolvers in order to implement some complex logic?
That one thing is what scares me away from serverless solutions. I've tried AWS AppSync and it was a nightmare to have to deal with having to write custom AWS Lambda functions that would overwrite the default methods and work with velocity template stuff etc. I'm now working with a Django API with Graphene for the GraphQL part and I like how much control it gives me in designing stuff. Of course the disadvantage is that it is not as straightforward and effortless to set up as what we're looking at here, but it pays off in the long run in letting us do some complex stuff that might crop up later on.
Hi, if I use hasura in my new project. Do I still need express or laravel backend? Sorry, I'm completely new to this
No, Hasura handles all of that for you. It serves you a GraphQL API which is connected to a postgres database
Ruston, you do not! This is all done on the hasura graphql engine, and does not involve any bulky frameworks or setups.
But (completing all you guys have said), if you have another API with Express, or whatever, and you want to apply this code onto your app, Hasura let you to join that external API to the GraphQL basic API that has been built with it. It's ridiculously awesome.
Hasura now handles cron jobs for you.
Hello, does this also work with an existing project having mLab (cloud mongodb database) if I follow through this tutorial? Schemas, type definitions and resolvers are already defined in the server. So I want to migrate an existing app to docker and Hasura.
Hasura works only with Postgres. Sorry, pal