For business logic, there are a few alternatives.

1. Actions - https://hasura.io/docs/1.0/graphql/manual/actions/index.html

2. https://3factor.app/

3. Remote schemas - https://hasura.io/docs/1.0/graphql/manual/remote-schemas/ind...

I'm running a full production algorithmic trading platform, and our frontend interactions are handled by Hasura. For me, the appeal was in writing all the business logic as Postgresql triggers, which (provided they're written as true SQL and not plpgsql), scale beautifully with load. Hasura has a real appeal when you're keen to do your important logic in SQL.

Check out the result here: http://www.hedgecheap.com

I'm considering trying Hasura (or preferably something that can run on SQL Server as that's what we use in production. For me it feels as if trying to do the entire app through Hasura is the wrong approach. But, if we apply CQRS and treat reads different than writes then if we just use it for all of the reads in the system it could eliminate a tonne of code for us. The transactional code can still all go through entity framework and rest APIs.

You may enjoy the work done by Julie Moronuki and Chris Martin. They do lots of great learning stuff related to haskell.

> How do we add business logic ?

Awkwardly. Good luck