Any egress IP assigned to that colo could be used, even changing between requests

I have 2 workers is it possible to make it were worker B can only be called from worker A without having to add custom domains and WAF rules? Trying to make it simple as possible.

Maybe Service Bindings is what you're after? https://developers.cloudflare.com/workers/platform/bindings/about-service-bindings/

Thank you, That does look what I'm looking for. Thank you

can anyone help me figure out how many UUIDs (v4) I could store in a single DO value (in an array)? I'm not sure how to get the V8 serialization size

js
const { serialize } = require("v8");
const crypto = require('node:crypto');

const serializedOne = serialize([crypto.randomUUID()]);
const serializedTwo = serialize([crypto.randomUUID(), crypto.randomUUID()]);

console.log(`Size one: ${serializedOne.length}`);
console.log(`Size two: ${serializedTwo.length}`);

const sizePerUUID = serializedTwo.length - serializedOne.length;
const fixedOverhead = serializedOne.length - sizePerUUID;
const durableObjectValueLimit = 131072;

console.log(`Max UUIDs allowed: ${Math.floor((durableObjectValueLimit - fixedOverhead) / sizePerUUID)}`);

3449 if my math is right

(disclaimer, I'm not on the team and I base my answer on some experience with workerd) It does look like you are correct in your case, if you store the uuid as a Uint8Array (conversion required both when storing & fetching to get the current form), I believe you can save more as they would only take up 16 bytes (+ overhead) instead of 36 (+ overhead)

thank you 😄

I wish CF had better support for long running tasks - Workers can already stay alive indefinitely as long as there is a request attached to it so why is there a tight limit on the length of

waitUntil

and Queue worker lifetimes? it makes long running background requests very tough to do 😦

maybe I should create a server with the sole purpose of opening long running connections to my worker to get past the limits 🤣

Should node_compat work in quick edit mode?

Uncaught Error: No such module "node:buffer".  imported from "worker.js"

Probably not

It does not

Would it be possible to self host elasticsearch on a cloudflare worker? And is this a good idea...?

I would be incredibly doubtful that that would be possible

Workers aren't long running processes - think of them as server-side service workers from a browser

yeahhh... I couldn't find any info on it and using elastic cloud seems a bit expensive for my current use case

Could I use another cloudflare tool for this? Like durable objects?

If you built it yourself, sure

I'm not sure I understand

You wouldn't be able to just run elastic search

You could build your own search on durable objects

Oh...

You'd probably find it easier to just get a VPS

Something like fly.io has a decent free tier

I'm looking for something cheap but still scalable

well cheap at the start, but can scale up and get more expensive

^ the cloud would probably be perfect for this - but most solutions are really expensive. Elastic cloud is around 35 - 40 usd a month

Unfortunately there's not really any CF product for that kind of thing

What's the reason that I can't run elastic search on durable objects?