Over the last couple of months Aista have experienced what I consider to be unethical business methods, where the feeling has been that somebody is "out to get us". Now of course, I am admittedly slightly more "paranoid" than the average guy, but when somebody registers a domain I consider is rightfully ours, and somebody opens a company in Japan sharing our name, delivering cloud services, it's easy to see why I reacted the way I did I presume.
I thought Hasura had something to do with it, and hence I became angry, and I started thinking about "how to get revenge". It seems Hasura is equally surprised as me about the situation, and I've spoken to Tanmai about it, and I believe him when he says Hasura has nothing to do with neither the domain issue nor the company in Japan parts. Hence, I owe Hasura an apology, which is one of the reasons why I'm writing this article.
I apologise to Hasura and Tanmai for blaming them for something they had nothing to do with.
Give me your GraphQL use case
I still believe Hasura and GraphQL doesn't have an adequate solution for business logic code, so I would love to reach out to the GraphQL and Hasura community and ask for specific use cases where they require business logic that's not adequately solved by GraphQL or Hasura. The point is to get ideas for articles where I will solve these problems using our own Hyperlambda, showing how we and Hasura can co-exist peacefully, and "play each other better", instead of perceiving each others as competitors. Hence ...
- Where did you get stuck with GraphQL and Hasura?
- What did you want to accomplish where you got stuck?
- What prevented you from moving forward at this point?
Answer the above questions in a comment here, and I might use your problem as an example for a use case which I will solve by creating a YouTube video, and writing an article here at DEV solving it using Hyperlambda. Below is one example of such a solution where I'm sending an email using Hyperlambda by creating an interceptor where I apply the business logic in Hyperlambda, before forward evaluating my GraphQL endpoint ...
Top comments (4)
IMO graphql is mostly a buzz word and not something you should implement until your project has matured or becomes a tangled mess. If all you're doing is building basic CRUD operations for a front-end app, there isn't really a need for graphql.
It's when you start to have an insane amount of nested relationships, that graphql becomes useful. Like when you're getting posts from friends of friends, or querying versions of ads within a category of posts visible to the current user.
Apps with complex data schemas tend to be harder to filter for specific end points. IMO graphql is the band-aid that fixes that problem.
I have no doubts your assessment is correct here. Unfortunately my and yours opinion about GraphQL is the minority report, and hence we're stuck with having to deal with it somehow.
Well honestly I don’t like graphql, but setting up a TheGraph node is much more easier and faster then implementing custom made chain crawler with crud like interface. In most cases it’s functionality is all you need to start a web3 project.
So yeah, that’s the business case
I was more thinking about what do use GraphQL for when doing custom development ...