3 ms·
Processing should be more like 6 ms though (assuming basic CRUD), not 60. The TLS/TCP latency can be solved with a TLS terminating proxy in the region. After th
by ndriscoll 2y ago
Processing should be more like 6 ms though (assuming basic CRUD), not 60. The TLS/TCP latency can be solved with a TLS terminating proxy in the region. After that, unless you want spinners on every data fetch (a miserable experience), you probably want a read replica if you're actually trying to serve the region. If you're a big company, you probably want a full read/write setup in the area (which is something for big companies to figure out anyway with newer data protection laws).
Slow server calls and daisy chained sequential operations are both people doing a bad job. My last job had backend calls that took over 1s to do basic CRUD on a low traffic service (bouncing around a dozen micro services on the backend). That should never happen.