This feels like Cloudflare using the strangler pattern to continue their march into established cloud provider territory.<p>Their serverless implementation is outstanding - AFAIK, they're the only ones offering true scale-to-zero compute with no cold start delays. I've used it successfully to host an SSR app that hits an external API basically at no cost. If I'm reading this correctly, I can now move the API code into Cloudflare Workers as well, and just leave the database at the old provider, with the promise of much lower cost-for-performance for compute and better database performance. Sounds compelling and helps to move chunks of infrastructure to Cloudflare, who will undoubtedly introduce hosted relational databases in the future to complete the picture.<p>I'm unclear about the security implications though. My current database is in a private subnet, it would be unfortunate to have to open it up to the world to take advantage of this. The other downer is that Workers don't natively support .NET, so I can't make that move yet. But it's certainly intriguing!
This is a solution to problem that does not exists. In database heavy apps the latency is the least of the concern. unless that architecture is not optimal in some cases to meet compliance.