https://hasura.io/blog/building-an-offline-first-web-app-wit...
https://hasura.io/blog/building-an-offline-first-web-app-wit...
It's this developer experience I want to mimic with Nhost. By providing a managed backend with simple to use js-sdk (https://github.com/nhost/nhost-js-sdk).
We chose this because :
1.Open source (no vendor locking although now i'm sure if i had to move from b4a it would be a small PITA 2. Ready to use 3. actively maintained (graphQL have been implemented although we have not used it yet) (3)
My question is : should i invest time on discovering nhost for my next POC ?
(1) : https://github.com/parse-community (2) : https://www.back4app.com/ (3) : https://docs.parseplatform.org/graphql/guide/
1. SQL (Thanks PostgreSQL)
2. Instant realtime GraphQL (Thanks Hasura)
3. Zero vendor lock-in
This is wrong. For basic features that are absolutely needed for a real-life app you will need the "Pro" hasura license.
Amazing at first, but quickly fell apart when I had to implement any sort of meaningful business logic.
2. Actions - https://hasura.io/docs/1.0/graphql/manual/actions/index.html
3. Remote Schema - https://hasura.nhost.io/console/remote-schemas/manage/schema...
I know Hasura is actively working on this exact issue and they just released Actions (second option) and I think we will start to see a standard/best practice approach to business logic soon.
@elitan - just checking nhost. Features sounds promising.
Did you use hasura for building nhost's backend as well ?