> So while AWS has 17 ways to run containers and 7 ways to do async message processing, all overlapping and reinforcing and supporting each other, Cloudflare will tend toward introducing singular primitives, stuff them in a box, and try to ship those boxes to as many places as will possibly take them. If they could install Cloudflare on your mobile phone, they would (this gets them dangerously close to being a real life Pied Piper).

I think this statement resonates with me the most - it feels a lot like how I prefer to design systems (ahem, thanks Unix!): simple pieces or types, chained together into systems that are easy to understand, maintain, and scale.

We're still only using Cloudflare's workers and it's integration with caching, but it's getting close to the point where I'd have enough primitives to ship some of the functionality of our system architecture to Cloudflare and gain a net-win for latency and simplicity.