If you love hasura and want something like firebase, please check out the tutorial with hasura + RxDB. It is like having a firebase with better offline-first and more features and of course without vendor lock-in.
What I liked with Firebase was how easy and fast everything was. One-click create a new project and everything was ready to use.
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).
I'm a web entrepreneur and for my project i've been using Parse server project (1) implementation by Back4app (2).
For the non initiated, Parse server is a API server module for Node/Express + mongo + websocket and stuff you need to run a commercial app like auth, role management et all.
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 ?
Yes I agree with you. With Hasura there are 3 main ways to handle business logic. We use the first one at Nhost and it's working (and scale) very well.
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.
https://hasura.io/blog/building-an-offline-first-web-app-wit...