Open galkin opened 1 year ago
Hi @galkin! Thank you for the request! We chose the polling approach for various security benefits. To support serverless, we'll need to implement a push version, which requires us to implement a different authentication mechanism. I'll bring it back to the team to discuss about it.
Making it webhook-based would be better for serverful environments as well. I just deployed Retool RPC today and we already get a lot of false-negative errors due to random network errors when the polling happens.
It'd be nicer if it was a webhook that got called (maybe with a debounced batch of messages in the last x milliseconds so we'd internally could leverage dataloaders etc for e.g. RPC-calls within lists of stuff)
@hdoan741 and @huytool157, i know that rpc is beta. There is my architecture feedback.
The current architecture for retool rpc doesn't support serverless architecture. Under the hood integration uses polling, which requires running server.
Our case:
We have such setup for cost optimization. From a security standpoint pull-rpc looks better than rest/graphql/grpc/etc, but we can not use it in QA environment.
Can we add the ability to call webhook from retool based on resource configuration? It should improve the Developer Experience with this resource.