Cloudflare Workers scale too well and broke our infrastructure, so we are rebuilding it on Workers

This post details how DevCycle rebuilt its infrastructure on Cloudflare Workers to handle extreme load spikes that overwhelmed their traditional AWS infrastructure. It describes moving event processing to a new Cloudflare Worker and Kinesis Data Firehose, and discusses architectural considerations for data management within Workers, including KV, Durable Objects, R2, and D1, highlighting the predictable cost structure of Workers. The post also mentions the use of WASM libraries for consistency across SDKs.