MNear-term roadmap for Hyperdrive:
- Land metrics & analytics (via the dashboard & GraphQL API) to make it easier to debug
- More controls around caching
- Continued performance improvements
- MySQL support (closer to end of year)
- Support for databases in private networks (Magic WAN, Cloudflare Tunnels) in early 2024.
CQuestion: are there any sort of egress IP ranges we can add to our firewall for hyperdrive->origin, or should we wait for CF tunnel support if we’re worried about public access?
MThe latter for now. We generally don't recommend IP ACLs like this, and would still allow any other customer to connect to your database (create a Worker, create a Hyperdrive to your DB, or a TCP socket). Only makes sense if we give each user a dedicated IP address, which isn't scalable.
CRight, that makes sense - super excited for CF Tunnel integration here then
Cwould also love to see a more general version of hyperdrive (or similar tech) for accessing private resources (IE so we can communicate with services back on our AWS VPC from a Worker via a secure tunnel)
MI think that's fundamentally just Workers + Magic WAN / Tunnels. You can connect to tunneled resources via a Tunnel from a Worker today, but we want to make it easier to set that up.
CYou can connect to tunneled resources via a Tunnel from a Worker todayah, I was unaware this was possible currently. Is it just the standard "things in your CF account can access the
$uuid.cfargotunnel.com bit?MYep. You can put Access in front and use a Service Token to auth as well.
CGotcha - I think I interpreted Hyperdrive's role as private connectivity + connection pooling, but makes sense the private connectivity is CF Tunnel. super excited again for the CF Tunnel integration!
IDoes this extend to TCP from Workers? I.e. via the Socket API or similar?
MTo be clear, Hyperdrive will build a lot of this in — but at some point you need to give us a way to get to that private resource, which has to be Tunnel or Magic WAN (IPSec, GRE, etc)
MNot yet.
SI have been waiting for this for a long time. Excellent Job
KDoes your connection string start with
postgres://?K(or
postgresql://)KIf you do
new URL(yourConnectionString).protocol in Node, what do you get?KKThe note about 3.8.0 doesn't look right either, Hyperdrive was added in 3.10.0.
KMight be another one to cover in your PR? @alex.robinson
UI mean always being warm would obviously be super nice but I think what matters more at least on the hobby project side is not paying for idle usage. For an actual business use though I do think even paying to keep connection always warm to reduce times is ideal
SWhat if we can configure the idle timeout?
