Dang, is there no easy way to talk to neon without using javascript?

Bbenthecarman Dang, is there no easy way to talk to neon without using javascript?

Not that I know of on Workers. The difficulty is that Workers uses a custom TCP socket implementation which means that drivers need to be specifically designed for it.

Isaac McFadyen•9/17/23, 11:35 PM

As far as I know only JavaScript (pg and postgres.js) drivers for Postgres have been modified to work so far.

benthecarmanOP•9/17/23, 11:37 PM

Dang that's unfortunate

benthecarmanOP•9/17/23, 11:43 PM

Filed this, hopefully someone picks it up!
https://github.com/cloudflare/workers-rs/issues/386

GitHub

[Feature] PostgreSQL Support · Issue #386 · cloudflare/workers-rs

Is there an existing issue for this? I have searched the existing issues Description Recently you guys have announced support for various database integrations https://blog.cloudflare.com/announcin...

benthecarmanOP•9/18/23, 12:07 AM

Oh wait just found this https://github.com/cloudflare/workers-rs/blob/main/examples/tokio-postgres/src/lib.rs

GitHub

workers-rs/examples/tokio-postgres/src/lib.rs at main · cloudflare/...

Write Cloudflare Workers in 100% Rust via WebAssembly - cloudflare/workers-rs

Rich•9/18/23, 2:36 AM

Does anybody know if it's safe to put

context.waitUntil

context.waitUntil

on the global to improve it's ergonomics or does it need to be coupled with a specific request? e.g.

// worker.js
import { myFetch } from './my-fetch';

export default {
  async fetch(request, env, context) {
    global.waitUntil = context.waitUntil;
    return fetch(request);
  },
};

// my-fetch.js
export const fetch = async (request) => {
  const response = await fetch(request); 
  response.headers.append("Cache-Control", "s-maxage=10");
  waitUntil(caches.default.put(request, response.clone()));
  return response;
}

// worker.js
import { myFetch } from './my-fetch';

export default {
  async fetch(request, env, context) {
    global.waitUntil = context.waitUntil;
    return fetch(request);
  },
};

// my-fetch.js
export const fetch = async (request) => {
  const response = await fetch(request); 
  response.headers.append("Cache-Control", "s-maxage=10");
  waitUntil(caches.default.put(request, response.clone()));
  return response;
}

JJames After their platform got hit with security issues. I would recommend avoiding Ma...

addison•9/18/23, 3:29 AM

is this not fixed now with the requirement for domain lockdown if using workers?

Aaddison is this not fixed now with the requirement for domain lockdown if using workers?

sathoro•9/18/23, 4:21 AM

if you care about deliverability and security I would use a service that does any level of manual domain verification which would be... all of them except Mailchannels. personally I recommend Postmark

Ssathoro if you care about deliverability and security I would use a service that does an...

addison•9/18/23, 4:23 AM

well don't you need to manually set a txt record on your domain now? so far I haven't seen any deliverability issues on my domains using mailchannels and they can't be triggered by another worker

Aaddison well don't you need to manually set a txt record on your domain now? so far I ha...

sathoro•9/18/23, 4:24 AM

I mean manual verification by a human, not automatic verification through a DNS record

sathoro•9/18/23, 4:25 AM

that's great, then continue using Mailchannels. I choose not to support companies who fail at core functionality and have had glaring security issues for years.

addison•9/18/23, 4:27 AM

to be fair I think there's a failure on multiple levels on most parties involved but yeah I can see why you would choose not to use mailchannels. I just like not having to pay to send emails which mailchannels is doing just fine for what I use it for and hopefully will continue doing so in the future.

RRich Does anybody know if it's safe to put `context.waitUntil` on the global to impro...

Hello, I’m Allie!•9/18/23, 7:20 AM

IIRC it is tied to the request

HHello, I’m Allie!IIRC it is tied to the request

Rich•9/18/23, 7:28 AM

Aww, that's a shame. I'm finding it causes me to have to pass

ctx

ctx

waitUntil

waitUntil

env

env

into various modules, creating a lot of boilerplate for call sites

RRich Aww, that's a shame. I'm finding it causes me to have to pass `ctx` or `waitUnti...

Hello, I’m Allie!•9/18/23, 7:39 AM

You can use

AsyncLocalStorage

AsyncLocalStorage

to pass request-bound variables around "globally".

AsyncLocalStorage · Cloudflare Workers docs

Cloudflare Workers provides an implementation of a subset of the Node.js AsyncLocalStorage API for creating in-memory stores that remain coherent …

HHello, I’m Allie!You can use [`AsyncLocalStorage`](https://developers.cloudflare.com/workers/runt...

Rich•9/18/23, 7:43 AM

Interesting, I'll take a look thanks

alotabits•9/18/23, 12:44 PM

How is cache.put coordinated when two concurrent requests in the same worker attempt to update the cache for the same cache key? Specifically in the case when both requests only .put after a .match failed. I’m assuming since there is no mutex or other lock mechanism that it’s basically “last request wins”.

simpson•9/18/23, 12:47 PM

We are looking to move all of our serverless functions to Cloudflare workers, one of the things we are trying to understand is how to best structure our project. Originally we wanted to have a single Worker, but with our 20-30 functions they each need their own different CRON schedules, so it seems like we'll have to make every function its own worker. However, there is a lot of shared logic between all these functions that i'd hate to duplicate many times over and have to try and manage that. Is there any best practices on how to build a large set of workers that can share libs and also have CRON flexibility?

Ssimpson We are looking to move all of our serverless functions to Cloudflare workers, on...

alotabits•9/18/23, 12:47 PM

Service bindings?

Ssimpson We are looking to move all of our serverless functions to Cloudflare workers, on...

sathoro•9/18/23, 12:48 PM

you could do a single worker and instead of using crons you could use durable object alarms

Aalotabits How is cache.put coordinated when two concurrent requests in the same worker att...

sathoro•9/18/23, 12:49 PM

probably yes

sathoro•9/18/23, 12:49 PM

the cache is per colo btw

Ssathoro you could do a single worker and instead of using crons you could use durable ob...

simpson•9/18/23, 12:59 PM

interesting! so bind a single worker to a DO and put all the scheduling logic there?

Ssimpson interesting! so bind a single worker to a DO and put all the scheduling logic th...

sathoro•9/18/23, 1:00 PM

sort of, but in your case you might want multiple DOs for each cron to simplify the scheduling. although I've also seen a library that would help with this (can't find it...)

Ssimpson interesting! so bind a single worker to a DO and put all the scheduling logic th...

sathoro•9/18/23, 1:05 PM

can make your own scheduler with a single DO (but multiple instances) like this using

itty-durable

itty-durable

import { createDurable } from "itty-durable";

export class Scheduler extends createDurable({ autoPersist: true }) {
  constructor(state, env) {
    super(state, env);
  }

  create(name, doEverySeconds = 30) {
    this.name = name;
    this.doEverySeconds = doEverySeconds;

    this.setAlarm(Date.now());
  }

  async alarm() {
    console.log(`Doing ${this.name}...`);

    this.setAlarm(Date.now() + this.doEverySeconds * 1000);

    // do the thing...
  }
}

import { createDurable } from "itty-durable";

export class Scheduler extends createDurable({ autoPersist: true }) {
  constructor(state, env) {
    super(state, env);
  }

  create(name, doEverySeconds = 30) {
    this.name = name;
    this.doEverySeconds = doEverySeconds;

    this.setAlarm(Date.now());
  }

  async alarm() {
    console.log(`Doing ${this.name}...`);

    this.setAlarm(Date.now() + this.doEverySeconds * 1000);

    // do the thing...
  }
}

sathoro•9/18/23, 1:05 PM

and the DO can import whatever code it needs to from your codebase directly

sathoro•9/18/23, 1:06 PM

(

itty-durable

itty-durable

is not needed, it just makes the code way shorter)

dave•9/18/23, 2:41 PM

Does

.fetch

.fetch

on a Service Worker binding do anything with the

cache-control

cache-control

header?

TTraffy Does worker supports mongoose or mongodb driver?

Legendarist•9/18/23, 4:35 PM

https://www.mongodb.com/developer/products/atlas/cloudflare-worker-rest-api/

Create a REST API with Cloudflare Workers and MongoDB Atlas | MongoDB

Learn how to create a serverless REST API using Cloudflare workers and MongoDB Atlas.

LLegendarist https://www.mongodb.com/developer/products/atlas/cloudflare-worker-rest-api/

Isaac McFadyen•9/18/23, 5:06 PM

That's Atlas only but yes.

Isaac McFadyen•9/18/23, 5:06 PM

(Atlas is their hosted service)

dave•9/18/23, 6:56 PM

Can I do a Worker service binding from Worker #1 in local mode (

wrangler dev

wrangler dev

), that goes to Worker #2 in remote mode (

wrangler dev --remote

wrangler dev --remote

dave•9/18/23, 7:02 PM

https://github.com/cloudflare/cloudflare-docs/commit/b03a8368f7f0b8a9eb89a7276baef894bad71078

GitHub

fix: cannot interact with service bindings locally (#9890) · cloudf...

The documentation provides a non-existent argument for

pages dev

pages dev

. Even if it is planned to add the functionality in future, right now the instruction is rather confusing than helpful.

dave•9/18/23, 7:02 PM

seems like no?

MetalGear•9/18/23, 7:35 PM

would you guys say that cloudflare workers are fully capable of building a hotel PMS system? I have seen alot of people use workers for MVP but wondering if you guys reccomend it for a scalable saas

MMetalGear would you guys say that cloudflare workers are fully capable of building a hotel...

sathoro•9/18/23, 7:36 PM

it scales yes

sathoro•9/18/23, 7:36 PM

Web Scale

MetalGear•9/18/23, 7:37 PM

in what cases would you guys say yeah go with monolith because cloudflare workers wont be a good fit for that

Unsmart•9/18/23, 7:51 PM

I would personally never go with a monolith

Unsmart•9/18/23, 7:51 PM

theres serverless cases for probably everything

Cyb3r-Jak3•9/18/23, 7:53 PM

I mean depends on the stack. If you need lots of pieces then monolithic can be easier to maintain and deploy

CCyb3r-Jak3 I mean depends on the stack. If you need lots of pieces then monolithic can be e...

MetalGear•9/18/23, 8:17 PM

I guess I’m just wondering what the limitations of cloudflare workers are. Is it recommended to build a whole saas hotel reservation system on it for example

Unsmart•9/18/23, 8:20 PM

Can you build a hotel reservation system on workers - yes. Should you? Do you know how to use cloudflare can you hire people who are good at cloudflare.

UUnsmart Can you build a hotel reservation system on workers - yes. Should you? Do you kn...

MetalGear•9/18/23, 8:25 PM

Yes I’d say I’m good at building apis on workers with honojs. I’m a one man team

MetalGear•9/19/23, 12:05 AM

does anyone know how I can make npx wrangler dev use data the is in my deployed worker. It was using it but its now stale for some reason

MMetalGear does anyone know how I can make npx wrangler dev use data the is in my deployed ...

Cyb3r-Jak3•9/19/23, 12:12 AM

Like a binding?

CCyb3r-Jak3 Like a binding?

MetalGear•9/19/23, 12:13 AM

No like I have DO persistent storage data in my deployed worker

MetalGear•9/19/23, 12:13 AM

I want to basically run npx wrangler dev and use the latest data that is in deployed worker.

MetalGear•9/19/23, 12:14 AM

I thought that happened automatically whenever I restart npx wrangler dev but for some reason its not right now.

MetalGear•9/19/23, 12:14 AM

I am using the latest version of wrangler btw

// worker.js import { myFetch } from './my-fetch'; export default { async fetch(request, env, context) { global.waitUntil = context.waitUntil; return fetch(request); }, }; // my-fetch.js export const fetch = async (request) => { const response = await fetch(request); response.headers.append("Cache-Control", "s-maxage=10"); waitUntil(caches.default.put(request, response.clone())); return response; }

import { createDurable } from "itty-durable"; export class Scheduler extends createDurable({ autoPersist: true }) { constructor(state, env) { super(state, env); } create(name, doEverySeconds = 30) { this.name = name; this.doEverySeconds = doEverySeconds; this.setAlarm(Date.now()); } async alarm() { console.log(`Doing ${this.name}...`); this.setAlarm(Date.now() + this.doEverySeconds * 1000); // do the thing... } }

Dang, is there no easy way to talk to neon without using javascript?

Similar Threads

Similar Threads

Similar Threads