Six Million Events, Three Minutes of Trouble
I wanted to know if a swamp datastore could survive a swarm, so I asked an agent to design one, pointed it at ECS Fargate, and stepped away. A custom Docker image, a fleet of remote workers, and a simple execution plan: model method calls firing events as fast as the workers could generate them. The final cluster ran 517 tasks: 500 loop workers each pushing telemetry at roughly 1.22 events per second, a single orchestrator running swamp serve against 50 models on a shard-first S3 datastore, and 16 serve-dispatch workers standing by for workflow batches. At full tilt that’s north of 600 events a second, sustained. The point was lock contention: S3 versus my Postgres extension, under real concurrent write pressure, the kind a global team of hundreds would eventually produce whether I tested for it or not. ...