Hacker News new | ask | show | jobs
by dvdhsu 1426 days ago
Yes, this is something our infra team is working on right now. As of today, somebody in Australia, with a database hosted in Australia, experiences two round-trips in order to get data (client => our backend => database => our backend => client). We are working on deploying our database connector in far more regions so this won't be a problem. I think ETA is ~next two months? Will check in with team now...

An alternative is our self-serve on-premise product: https://retool.com/self-hosted/, which you can host in your own EC2. Given this latency issue is our fault, if you want a discount, just reach out to me; I'm david AT. Happy to provide a discount until we go multi-region with our backend.
1 comments
snir 1426 days ago
Hi all, I'm Snir -- I lead engineering here at Retool.

I wanted to follow up on the above. Solving the round trip problem David mentioned above involves multi-region for our entire backend, inclusive of our DB. This is definitely a priority and something we plan on having by EoY.

link
doctor_eval 1426 days ago
Hi, thanks to both for your answers. I could see that it was a round trip problem, and it’s good to know you’re aware of it. Despite trying really hard, the latency made it unusable.

Also IIRC, there was way more than 2 round trips .. I think my UI made a few (GraphQL) API calls and they appeared to be serialised, so it really was in the order of 1-2 seconds for a page to load. This was 18 months ago so both my memory and your implementation might have changed since then.

In terms of using retool, unfortunately that particular ship has sailed for me, but I’ll be quite happy to reconsider it in any of my new projects once you have a solution that is a couple of hundred light-milliseconds closer :)

link