Hacker News Reader

pvheeon The nightly Ralph loop: a coding agent that works my backlog and never merges

Author here. Thought about sharing how I had escaped chatting to 10s or 100s of agents to a worfklow that is much more hands-off and allows work with less distractions, all the while increasing throughput substantially.

I'm currently rolling this loop across different projects and teams as well and exciting to see how far this takes us on producing quality products. Happy to answer any questions on this workflow.

pvheeon How we processed €5M in donations in 2 hours using Cloudflare and Stripe

If you can push services to the edge without adding complexity to your setup, why wouldn't you? The simplicity (and pricing model) of running code on Cloudflare Workers should be reason enough to do this.

I agree that AWS Lambda for this project would have been more than sufficient, together with S3 for static hosting. However, the advantage of CF workers over is that you combine both the CDN, static hosting, the API layer and the back-end logic running in one and the same worker, therefore significantly simplifying your setup.

With AWS (and without using Lambda@Edge), we'd probably have to use a combination of Cloudfront, S3, API Gateway & Lambda. All of these could easily be defined in code with something like the Serverless framework or AWS SAM, but there are a lot more moving parts here when compared to CF Workers.

pvheeon How we processed €5M in donations in 2 hours using Cloudflare and Stripe

Total infrastructure cost is less than 100 USD, but this is an estimate.

As this was directly deployed onto RTE's Cloudflare account, we don't have the breakdown for this. However if we count around 4 million requests at 0.5 USD / million requests, you can see that costs from the serverless infrastructure itself are negligible at a few dollars only.

The major "infrastructure" cost stems from Sentry, which we used for application monitoring & crash reporting. We're on the team plan at 29USD / month with added on-demand spend of 100 USD, which we've nearly exhausted considering a large number of events were sent to Sentry. We had also enabled spike protection, which means we're paying less as certain events are rate limited in any given minute to avoid massive overspend (which we would have certainly run into).