undefined

points

[-]

Predictability matters. The whole point of paying someone else to handle a problem for you is that you don't have to worry about it. If you go all in on a provider and then suddenly find out that you've been switched to a paid plan in the middle of your vacation, that's not a place anyone wants to be. Saying there's no lock-in is nice, but that overlooks the fact that there most definitely is friction. What if there's no mass export? No mass import? Or you need to reset 2FA? Or etc, there's a thousand things that can shoot you in the foot, especially if you have a lot of services you need to migrate.

by broken-kebab6 hours ago|

parent|

[-]

It's impossible to generalize over free vs paid in regard to predictability. E.g. a provider I paid for simply disappeared once when I was quite busy while my old free gmail still works. Realistically CF's free tier is more predictable than many paid options on market.

by Kye3 hours ago|

parent|

[-]

My threat model here focuses on what the provider gets out of the free tier. Cloudflare gets a broad view into activity on the internet for building the models they use for their paid offerings. Free Gmail puts people on a path in to Google's ecosystem with basically zero marginal cost.

by akdev1l5 hours ago|

parent|

prev|

[-]

>What if there's no mass export? No mass import? Or you need to reset 2FA?

1. For DNS we have standardized AXFR requests which the DNS provider needs to support as they are part of the DNS standard. There is not an option of not having that unless you have a really shitty provider that you should change anyway.

2. Same for Mass Import because again DNS already defines these things at the protocol level.

And resetting 2FA or whatever is just the cost of using any service

Personally I have used CF for ~10 years so I have saved $240 and I simultaneously use GitHub Pages and CF Pages for CDN because again I just need to give them a bunch of static files. Adding a third CDN provider would literally be a single command at the end of my build pipeline.

by edoloughlin6 hours ago|

parent|

prev|

[-]

Or your provider randomly decides you need to be on an enterprise plan: https://robindev.substack.com/p/cloudflare-took-down-our-web...

by gordonhart7 hours ago|

prev|

[-]

For personal projects, I'd rather just pay $2/month and not think about it than get hit with a random bill and scramble to migrate before the next month's bill. Bunny is perfect for this use case where you have a handful of projects that aren't all actively maintained. It just works without hand-holding, and since you're paying for the service, there's no rugpull looming.

by xur174 hours ago|

parent|

[-]

Don't you still have to worry about big bills since bunny bills based on usage?

by gordonhart3 hours ago|

parent|

[-]

The biggest bill I've gotten from Bunny was like $10 when my app (https://atlasof.space) briefly went viral and got 100k+ views in a month. Bunny CDN is so reasonably priced and the realistic visitor ceiling for my projects is low enough that it's still negligible. The free->paid cliff is typically a lot steeper than this in my experience.

by wonger_3 hours ago|

parent|

prev|

[-]

https://support.bunny.net/hc/en-us/articles/360000235911-How...

> Minimum Account Balance

> In order to keep your service online, you are required to keep a positive account credit balance. If your account balance drops low, our system will automatically send multiple warning emails. If despite that, you still fail to recharge your account, the system will automatically suspend your account and all your pull zones. Any data in your storage zones will also be deleted after a few days without a backup. Therefore, always make sure to keep your account in good standing.

You proactively replenish your balance, so in the worst case, you can just let the account go.

by osigurdson7 hours ago|

prev|

[-]

I didn't downvote it, but I don't think migrating away from Cloudflare workers, R2, D1, etc., isn't going to be that easy. Basically, the build these things from the ground up to work optimally for their infra - even the mental model that you have to use is different. If you only narrowly use one part of it, maybe.

by akdev1l5 hours ago|

parent|

[-]

>Cloudflare workers, R2, D1, etc., isn't going to be that easy.

And how is that related to me? My comment said (and the parent I replied to) mentioned DNS and CDN.

Now we add compute services, data storage, whatever D1 is and the other comment mentioned auth/authz

Are people not aware what CDN and DNS are?

by nixosbestos7 hours ago|

prev|

[-]

I used to handwave cloud portability. Turns out when you're shipping things and need extra services and you have deadlines, you build against the platform. I think the GP comment was probably expressing wariness of the free cloudflare tier that entices you to build against their APIs and their product shape in a way that inevitably locks you in. Sure, you could migrate, but that's expensive.

by glhaynes7 hours ago|

parent|

[-]

Yeah, good point. For a little hobbyist site of no importance, I'm not too worried about vendor lock-in, but that calculus changes as it gets more important.

by nixosbestos6 hours ago|

parent|

[-]

That's the catch though. By time you're scaling, there's tension between roadway and revenue and headcount and it's the worst worst possible time to need to reachitect.