Hello Retool Community,
I'm currently exploring ways to optimize the performance of our Retool applications, particularly concerning API response times. We've been using the cloud-based version of Retool, but we've noticed that our queries and API calls are taking over a second to respond, which is not as fast as we need.
Our backend services are hosted in the South-East region on AWS, while I suspect that Retool's cloud services might be operating from a different geographical region, likely in the US. This geographical disparity, I believe, could be a contributing factor to the latency we're experiencing.
Given this context, I'm considering the possibility of switching to a self-hosted Retool setup within our Kubernetes cluster, located closer to our backend services. My hypothesis is that by reducing the physical distance between the Retool interface and our backend, we might see a significant improvement in the responsiveness of our APIs.
Before making this transition, I'd like to gather insights from the community:
- Has anyone experienced similar challenges with API latency using the cloud version of Retool?
- For those who switched to a self-hosted model, did you observe noticeable improvements in API performance?
- Are there specific considerations or best practices to keep in mind when migrating to a self-hosted environment, particularly concerning Kubernetes deployment?
I'm eager to hear about your experiences and any advice you might have. Your insights will be invaluable in helping us make an informed decision and potentially enhance our application's performance.
Thank you in advance for your time and input!