TCP Connection issue
I’m connecting a Durable Object to a Neo4J database via TCP, which has worked flawlessly so far but for some reason it now takes more than 10 seconds for it to connect.
I’ve rolled back to previous versions of my worker but the problem is still occurring. I also don’t encounter this issue locally.
Any ideas what could be the cause? It’s been an issue for several days.
3 Replies
did you figure this out? also is the code for the connection to the neo4j database something you can share? @Victor
i'd like to use aura from workers, but they don't support http 😦
i'm replacing node.tcp with this cloudflare sockets implementation https://github.com/porsager/postgres/blob/master/cf/polyfills.js
GitHub
postgres/cf/polyfills.js at master · porsager/postgres
Postgres.js - The Fastest full featured PostgreSQL client for Node.js, Deno, Bun and CloudFlare - porsager/postgres
@Victor did you add a transpilation step to the worker build process and point it to neo4j?