How do I use hyperdrive with node-postgres in pages?
Original message was deleted
XDid some research, turns out you cant use hyperdrive with pages yet.
JThis is what I am currently doing to connect to a postgres db from within pages using the pg driver
1) Create a pages application, for mine I am using Remix.
2) Setup a worker called
3) Setup drizzle with an http proxy in your pages application. The pages app can use a service binding to call the
4) Make requests with drizzle, they will be proxied to your pages worker and your pages worker will use the connection pool from Hyperdrive.
With this setup you can connect to any postgres db.
1) Create a pages application, for mine I am using Remix.
2) Setup a worker called
pg-proxy that has a binding to a Hyperdrive instance. Use the Hyperdrive connectionString with the pg driver in the worker.3) Setup drizzle with an http proxy in your pages application. The pages app can use a service binding to call the
pg-proxy worker directly.4) Make requests with drizzle, they will be proxied to your pages worker and your pages worker will use the connection pool from Hyperdrive.
With this setup you can connect to any postgres db.
PAny performance costs associated with the proxy versus official pages support? It’s an extra hop right?
P@jensen
Jextra hop to a service bound worker
YPages does support Hypedrive binding now!
Mbut how do the bindings help when we cant communicate using postgres? or even if lets say one is using a serverless driver with drizzle, you get the: Uncaught TypeError: Failed to establish the WebSocket connection: expected server to reply with HTTP status code 101 (switching protocols), but received 530 instead.
Uncaught TypeError: Failed to establish the WebSocket connection: expected server to reply with HTTP status code 101 (switching protocols), but received 530 instead.\n at next-on-pages-dist/webpack/6783d7bf090fcdc3007a3c15fe2df2be.js:4:45633\n at async cs.execute (next-on-pages-dist/webpack/6783d7bf090fcdc3007a3c15fe2df2be.js:10:35832)\n at async T (next-on-pages-dist/functions/api/v1/rooms/[roomCode].func.js:1:8693)\n at async next-on-pages-dist/webpack/1fd9896c6b9aebf987ea59c84902706d.js:10:28664\n at async me.execute (next-on-pages-dist/webpack/1fd9896c6b9aebf987ea59c84902706d.js:10:26376)\n at async me.handle (next-on-pages-dist/webpack/1fd9896c6b9aebf987ea59c84902706d.js:10:29936)\n at async P.handler (next-on-pages-dist/webpack/1fd9896c6b9aebf987ea59c84902706d.js:10:22009)\n at async ke (next-on-pages-dist/webpack/1fd9896c6b9aebf987ea59c84902706d.js:10:3608)\n at async Module.<anonymous> (next-on-pages-dist/functions/api/v1/rooms/[roomCode].func.js:1:12317)\n at async C (bundledWorker-0.5240602707618374.mjs:1889:15)
Uncaught TypeError: Failed to establish the WebSocket connection: expected server to reply with HTTP status code 101 (switching protocols), but received 530 instead.\n at next-on-pages-dist/webpack/6783d7bf090fcdc3007a3c15fe2df2be.js:4:45633\n at async cs.execute (next-on-pages-dist/webpack/6783d7bf090fcdc3007a3c15fe2df2be.js:10:35832)\n at async T (next-on-pages-dist/functions/api/v1/rooms/[roomCode].func.js:1:8693)\n at async next-on-pages-dist/webpack/1fd9896c6b9aebf987ea59c84902706d.js:10:28664\n at async me.execute (next-on-pages-dist/webpack/1fd9896c6b9aebf987ea59c84902706d.js:10:26376)\n at async me.handle (next-on-pages-dist/webpack/1fd9896c6b9aebf987ea59c84902706d.js:10:29936)\n at async P.handler (next-on-pages-dist/webpack/1fd9896c6b9aebf987ea59c84902706d.js:10:22009)\n at async ke (next-on-pages-dist/webpack/1fd9896c6b9aebf987ea59c84902706d.js:10:3608)\n at async Module.<anonymous> (next-on-pages-dist/functions/api/v1/rooms/[roomCode].func.js:1:12317)\n at async C (bundledWorker-0.5240602707618374.mjs:1889:15)
