So right now actions are more kinda like extensions to hasura-engine right ? which you can perform intermediately. Right now I guess the issue is it still uses REST API to do that to perform an actions as web hook since Hasura is also considering on moving towards AI and ML applications with VectorDB. I felt there can be something that can be done here !
Describe the solution you'd like
Well the solution is considering graphql federations from Apollo. This involves using hasura as a gateway server to extend the use of actions, eliminating the need to use HTTP-based REST endpoints. By adopting this approach, hasura can become the central GraphQL-based gateway for applications, allowing for more flexible and efficient handling of actions.
@silicon-ninja
Here is the latest doc about Hasura's Multi-protocol Data Federation. As you can see, we support Federations involving actions, for certain use cases.
Is your proposal related to a problem?
So right now actions are more kinda like extensions to
hasura-engine
right ? which you can perform intermediately. Right now I guess the issue is it still uses REST API to do that to perform an actions as web hook since Hasura is also considering on moving towards AI and ML applications with VectorDB. I felt there can be something that can be done here !Describe the solution you'd like
Well the solution is considering
graphql federations
from Apollo. This involves using hasura as a gateway server to extend the use of actions, eliminating the need to use HTTP-based REST endpoints. By adopting this approach, hasura can become the central GraphQL-based gateway for applications, allowing for more flexible and efficient handling of actions.Describe alternatives you've considered
nope
CC: @SimratHasura