Comment by internetter

Comment by internetter 3 days ago

2 replies

> If you’ve built your app around their vendor specific stuff like Cloudflare functions, that can be bad news.

There's nothing that "special" about Cloudflare Workers, its mostly "just" a WinterCG runtime. Where you'd encounter problems is if you used the provided interfaces for other adjacent Cloudflare products, like R2, D1, KV, Queues, ect. So what you do is commit a hour of engineering time to make wrapper functions for these APIs. If you're feeling extra spicy, commit another hour of engineering time to make parallel implementations for another service provider. If you allow your tech stack to become deeply intertwined with a 3rd party service provider, thats on you.

grapesodaaaaa 3 days ago

Yeah, I guess that’s what I really meant.

Also at face value, it may seem like “an hour of engineering time,” but I think cloud vendor lock in is real unless you try very hard to only use abstract constructs.

  • notyourwork 2 days ago

    Agreed, I’m wondering where all these magical 1-hour efforts come from that decouple someone from a vendor. Let me just decouple from s3 real quick.