Yes, that is correct. We've kicked
Yes, that is correct. We've kicked around opening it up more, but have not committed to that yet. Hyperdrive operates as a standalone service, so it is technically possible, though would take some work.
If you're willing to discuss your use case a bit, it'd help us as we evaluate.
1 Reply
Pretty simple use case. We have a database that is currently in US East, but gets consumed from the west coast, Europe, and SE Asia.
Right now now we're using read replicas to reduce latency between the regions, with all the costs and complexity that comes with it. Lowering latency even a little could remove the need for some of these replicas (at least West Coast and Europe), and query caching could improve performance even further. We have an enterprise Cloudflare plan, so the whole "No additional extra costs" for Hyperdrive would be a great value add for "free" for us.
especially if it ends up exposed as just a passthrough to Postgres (so I could connect to it using regular drivers with no change to my app aside for the connection string)
Our frontend and backend-for-frontend are in workers, but the database connections are made from a .NET service living in Azure for historical reasons and in-house investments on that tech stack, thus why the db connection isn't made from the worker)