Is smart placement not recommended for applications with globally spread databases? e.g. traffic in
Is smart placement not recommended for applications with globally spread databases?
e.g. traffic in Chicago convinces smart placement that ORD is the optimal colo to complete requests in, as there is a DB in Chicago awaiting writes...
Will traffic from California, be routed through the ORD worker?... considering there will also be a closer DB within California they will (by design) have to hit anyway
Or will smart placement eventually learn that California and Chicago traffic has to be specifically ran in different colos
e.g. traffic in Chicago convinces smart placement that ORD is the optimal colo to complete requests in, as there is a DB in Chicago awaiting writes...
Will traffic from California, be routed through the ORD worker?... considering there will also be a closer DB within California they will (by design) have to hit anyway
Or will smart placement eventually learn that California and Chicago traffic has to be specifically ran in different colos



