CF’s Durable Objects product which I neglected to mention above attempts to be that huge database and cache. The CAP theorem isn’t violated, it just embraces co

CF’s Durable Objects product which I neglected to mention above attempts to be that huge database and cache. The CAP theorem isn’t violated, it just embraces consistency while relying on the partition tolerance of their POPs and backbone. Their KV store is more about availability. https://blog.cloudflare.com/durable-objects-ga/ https://blog.cloudflare.com/durable-objects-ga/ I don’t disagree that a huge database can handle an astonishing amount of load but at often unreasonable expense. There as many cases where FaaS is dramatically more affordable to run, both in compute cost and ops time. There are others where its costs spiral out of control under load and with dev effort to fit its constrained programming models. Its hard to say its entirely a trendy frivolity when there are many use cases where its the best tool for the job.