Post

with tap bandwidth do you mean ingress or egress? the full firehose does add up to a lot of ingress every month, but that is no-cost with many hosting providers. in theory you could split out just the tap part to one of those, and keep the rest of your setup where it is

That’s kinda where I ended up. I’m currently running tap on railway and sending webhooks to Cloudflare to handle data processing, but since it’s getting so many records it’s pushing egress costs up.

I did some deeper digging around my billing for Railway which has been the primary cost, and its kinda split between egress and CPU. Currently switching to a durable object on cloudflare that listens to jetstream which should help a bunch.

0 reposts1 like

Yeah that's a good way forward for something like this. Data integrity wise the downside of jetstream is it doesn't handle sync events (the new ones in sync 1.1). I'm not sure how common these are in practice but if you absolutely must consume every commit you need to handle these in the listener