Re:AWS is playing chess, Cloudflare is playing Go
by star-trek-fleet on Monday October 18, 2021 @05:46PM
(#28912216)
> 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.
Actually AWS also "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."
It's just that AWS covers such a larger terrotery, that they appear fragmented.
This is why I now almost don't read this type of macro-analysis articles. They themselves lack the overall birds-eye view, because they are usually produced by people with little concrete technical background.
They often is very good at producing analogy, which is very intuitive, but very easily breakdown after moderate amount of details.
Re:AWS is playing chess, Cloudflare is playing Go
by chrisweekly on Monday October 18, 2021 @04:13PM
(#28911019)
Cool. When you chose CloudFlare, did you also look at Fly.io?
Re:AWS is playing chess, Cloudflare is playing Go
by FunnyLookinHat on Tuesday October 19, 2021 @09:34AM
(#28917910)
At the time we picked CloudFlare, Fly.io wasn't really on ours or anyone else's radar yet. I've been meaning to experiment with Fly.io and Fastly - thanks for the reminder!
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.