Hasura connects to databases and all your other APIs to give a unified GraphQL API (and REST API, if you configure it).
This takes care of your CRUD APIs portion of building your app. With declarative Access Control Rules, you get powerful Authorization. IMO, these two should take care of 70% of your application code that you typically end up writing. The remaining will be custom business logic that you can write in any language or framework of choice and connect it to Hasura.
There’s of course more with the cloud offering to give you caching, rate limiting and monitoring in production. Hasura doesn’t host your database, it just needs the db connection string to get started.
I think Firebase has the lowest barrier to entry and if you don't exceed the pricing tiers, its a very pleasant experience.
Hasura and Prisma are both awesome, but after having worked in GraphQL a lot, I now try to stay at least 10 feet away at all times from GraphQL paradigms unless their hidden costs can be justified for the project.
I haven't used Thin, but it looks like its React only. If there was a Svelte or JS agnostic option Id give it a try.
I don't see anything in there about this including plans to build their own native data store. Nor do I suspect that would be a great idea (really really hard, not their competency, nor their point of leverage!)
Cloud Firestore so much easier than deploying a rails app somewhere. It comes with a lot of great analytics tools. The auth stuff works great. The documentation is very good. It has been extremely reliable. Syncing across devices is amazing and seamless in my experience.
If it fits your use case (I think mostly CRUD apps with data sharing that is somewhat limited in its breadth, e.g. not something like twitter with N-N data relationships), it is really amazing.
It has most of the features that all this shiny new tools have (and more) but is way older. It used to be a Facebook hosted solution but it was opensourced and is still actively maintained, has SDKs for most languages and frameworks, REST & Graph QL API, live queries... And there are still some sites that host it for you for free (limited), but you can always self host it yourself...
yes please, sign me up !!! /s
Bandwidth is frequently used in the context of file storage which can get expensive really fast even with a few users.
This doesn't translate well on the data side where most json responses will likely be lower than a few kb.
It's extremely unintuitive which is why I think most Paas providers use request and inflate the number (10 million requests sounds a lot in comparison).
We will update the pricing later today to make it more intuitive.
The Local API’s are a joy to work with. The capabilities of the local database makes Firebase look like a toy, and the sync service does solid two-way replication between devices.
Definitely one of the best backend-as-a-service we have tried (but our experience is mobile only, so yemv).
You should try both and see
As for your preference for Hasura security vs Postgres' native row level security, of course your preference is entirely valid and may also be the best fit for your needs, but consider that RLS works for all database clients, not just Hasura, so if you have a heterogeneous db client environment and you want to enforce one central policy, RLS can do that but a Hasura specific policy checker can't.
Disclaimer: I work at Supabase but not directly on the GraphQL support.
However, while I've played around with most of the others you mention, I haven't build anything serious with them. But hasura has a decent authentication story and reactive graphql queries are just a really nice dev experience
they are listed
disclaimer: we use them in our internal infra