4 ms·
There are plenty of exceptions to this, but as a general rule: Should: mostly front end app where your need a mostly CRUD style access to a backend with permis
by maxcan 5y ago
There are plenty of exceptions to this, but as a general rule:
Should: mostly front end app where your need a mostly CRUD style access to a backend with permissions that can be expressed using their DSL and are comfortable with all your back end logic being in lambda functions.
Should not (and this is a stretch for me since I love hasura): a large high amount of idiosyncratic backend logic that you don’t want to but in lambda functions but want more of running app servers. For example, I wouldn’t put something like a Twitter or clubhouse clone on hasura. However, I may run some sub services on hasura.
- praveenweb 5y ago> with all your back end logic being in lambda functions. Although this is recommended for NoOps and Scale, you can technically run all your backend logic on any full fledged servers that can run anywhere. Hasura just requires a HTTP endpoint for custom logic.
- sorenbs 5y agoMany prisma.io users tell us that they use prisma to implement complex business logic and then stitch it all together in hasura which exposes the final graphql API. So it might even be feasible to use Hasura for more complex applications. I'm curious if there are specific reasons you see this not working well?
- maxcan 5y agoNot really. I had to kind of steel man the anti hasura case since I overall agree with you.