Great concept and very real application. Adding Cloudflare Workers with D1 & R2 binding would be a nice addition to your list. As you said AI generated apps are being produced ten to the dozen at the moment with a number of them being deployed to CF workers, aided by how easy CLI/binding setup is.
What should it look for though? (items/challenges I've personally had to deal with, so yes, I'm being self-centered on the needs for this one)
- Race conditions on read-then-write SQLite/D1 queries. I've found with some Agents that they write non-atomic SELECT then UPDATE logic instead of atomic single-statement updates, causing breaks under concurrent requests.
- Unbounded subrequests or missing idempotency checks on third-party webhooks. Example being Stripe retries triggering duplicate writes.
- Blowing the 10ms/50ms Worker CPU time limit on unindexed queries or heavy JSON parsing.
Quick question on how your simulated backend works. Does it automatically fake the database tables on its own by reading the code or do you have to provide either the real or a sample schema first?
Hi Stephan,
Great concept and very real application. Adding Cloudflare Workers with D1 & R2 binding would be a nice addition to your list. As you said AI generated apps are being produced ten to the dozen at the moment with a number of them being deployed to CF workers, aided by how easy CLI/binding setup is.
What should it look for though? (items/challenges I've personally had to deal with, so yes, I'm being self-centered on the needs for this one)
- Race conditions on read-then-write SQLite/D1 queries. I've found with some Agents that they write non-atomic SELECT then UPDATE logic instead of atomic single-statement updates, causing breaks under concurrent requests.
- Unbounded subrequests or missing idempotency checks on third-party webhooks. Example being Stripe retries triggering duplicate writes.
- Blowing the 10ms/50ms Worker CPU time limit on unindexed queries or heavy JSON parsing.
Quick question on how your simulated backend works. Does it automatically fake the database tables on its own by reading the code or do you have to provide either the real or a sample schema first?