Egress costs are killing us. Any hacks?

2 pointssagar-co2 comments

We have some pretty heavy serverless / cloud functions usage. The cost of serverless compute is fairly less and we really like the pay-for-usage pricing.

Its extremely frustrating to pay for egress price to move the data around.

Checked Cloudflare Workers. We love it, but as of now, it does not support the packages we are using.

Are there any hacks around it?

View on HN

Can you talk more about your use case? What data are you moving around all the time via serverless? Like you're actually egressing large amounts of embedded data in the serverless func itself?

Like basically I wonder if there's a way to make the dataset itself more static and only use the serverless function to do some minimal processing on a chunk of it at a time. Maybe extracting the relevant code of that lib and putting it inside a cheaper serverless platform. They're typically best for frequent small operations instead of any heavy crunching. But it's not clear whether that even makes sense for your use case because I can't tell what you're trying to do with the limited info provided.

Can't you just compile to WebAssembly and use it in Cloudflare Workers? Then you have no dependency nonsense.

Like this: https://developers.cloudflare.com/workers/runtime-apis/webas...

Reply on news.ycombinator.com