The docs mention that workers bound to a d1 database are always placed in a datacenter near the loca
The docs mention that workers bound to a d1 database are always placed in a datacenter near the location of the db (https://developers.cloudflare.com/workers/configuration/smart-placement/#d1). Is this a limitation of the beta that will change once read replicas are a thing?
That same page indicates later that you can split up workers into front/backend workers that communicate using service bindings (https://developers.cloudflare.com/workers/configuration/smart-placement/#best-practices), suggesting one would be placed close to the user and the other close to the backend resource. This seems like it could help today if I could put the d1 bindings in the backend, but I'm a bit confused as to how this would work since the service binding docs seem to indicate that workers using service bindings are on the same machine? (https://developers.cloudflare.com/workers/runtime-apis/service-bindings/ mentions same thread, no internet)
That same page indicates later that you can split up workers into front/backend workers that communicate using service bindings (https://developers.cloudflare.com/workers/configuration/smart-placement/#best-practices), suggesting one would be placed close to the user and the other close to the backend resource. This seems like it could help today if I could put the d1 bindings in the backend, but I'm a bit confused as to how this would work since the service binding docs seem to indicate that workers using service bindings are on the same machine? (https://developers.cloudflare.com/workers/runtime-apis/service-bindings/ mentions same thread, no internet)

