I feel they are fairly early on in there “full stack” strategy. I believe they are moving quickly from launching MVPs for various products to expanding them as rapidly as they can. They are also purposely not trying to compete 1:1 with the incumbents with the “full stack”

“Workers” is brilliant, but the strategy with WASM on it is where I really think it is going to shine. The more languages and more of your stack that can be compelled to WASM the more you will be able to run on their edge. I truly believe WASM is the future in so many places other than in the browser.

I also feel the one part of their stack that’s missing is a transactional acid database (I hope for sql, but nosql would be fine). But it highlights a fault with the “edge first” strategy. Workers at the edge making multiple round trip requests to a central database is slower than running your app closer to the db. My wish is that they are developing some sort of edge replaced db that automatically launches read replicas at the same edge locations as where most of your worker load is. You probably have to have the main/master in a central location though. (I think Fly.io are doing something a little like this with Postgres)

Interesting. I like that whole view of a product. Like how do you describe Cloudflare's produce in one sentence.

Maybe something about 'large edge network cloud to reach your customer quicker' or something I'm not sure how to describe it in a compelling way. Maybe sprinkle on some web3 or distributed bs.

I think AWS, now Google is getting there, have that a lot of stickyness because it has all the services imaginable interconnected (not well sometimes but still). It's a platform not individual products. It's hard to pickup and leave, especially if Cloudflare doesn't have 1:1 replacements.