Absolutely — I agree with much of what’s been said. Cloudflare DOs bring strong advantages, such as
Absolutely — I agree with much of what’s been said. Cloudflare DOs bring strong advantages, such as automatic geo-routing to the nearest instance, security, infra, and more. Rivet, on the other hand, gives you the flexibility to stay within that ecosystem or branch out to other platforms to overcome limitations like tight resource caps or vendor lock-in.
What really stands out is Rivet’s clean API and documentation. It’s impressive, offering several capabilities Cloudflare doesn’t (at least not yet). Rivet won’t replace DOs anytime soon, but projects like this are healthy for the ecosystem. Brayden built Outerbase and it pushed the industry forward, to everyone’s benefit. While I don’t expect Rivet to follow the exact same trajectory, I do think it sends a strong message that should motivate the DO team to address current constraints and refine their trade-offs.
What really stands out is Rivet’s clean API and documentation. It’s impressive, offering several capabilities Cloudflare doesn’t (at least not yet). Rivet won’t replace DOs anytime soon, but projects like this are healthy for the ecosystem. Brayden built Outerbase and it pushed the industry forward, to everyone’s benefit. While I don’t expect Rivet to follow the exact same trajectory, I do think it sends a strong message that should motivate the DO team to address current constraints and refine their trade-offs.
