Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Free cloudflare VS Cloudflare+BunnyCDN
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Free cloudflare VS Cloudflare+BunnyCDN

Does anyone uses the cloudflare+BunnyCDN combination ? It is better than using the free cloudflare only ? Which is your feedback from them ? I wish to use cloudflare for DNS and proxy and some ddos protection and bunnycdn for images ,fonts ,css,etc. Can i got the better of both worlds for 12 dollars/yearly ?

Thanked by 1vyas11

Comments

  • No

  • How many different brands of condoms would you like to put on at the same time?

  • @poisson said:
    How many different brands of condoms would you like to put on at the same time?

    Just curious if i could improve my performance using bunnycdn condom ;)

  • Use CloudFlare and don't mind the others.

  • BunnyCDN ain't bad but from my testing doesn't bring much in term of speed compared to CF free as CF free will have less locations but your visitors won't waste time resolving a subdomain.

    Another option would be to use bunny's storage for your static assets, when "GEO Replicated Storage Zone" will be available, that way CF can fetch your files quicker. Not needed in most cases though, as that would just make the first lookup faster if you have a well thought caching strategy (and if you don't why bother using CF at all?).

  • BunnySpeedBunnySpeed Member, Host Rep
    edited November 2019

    Obviously biased, but I do get asked this a lot, so from our point view, besides features, the biggest benefits for a small website are the better cache hit rate and a more consistent performance, since at least in the past, CloudFlare on the free tier would in some cases simply route some parts of Asia or Australia to the US during peak hours for example and as loe mentioned they don't use all the PoPs on the free accounts. In terms of pricing, can't really beat free though :smiley:

    @greatgreat55 said:
    Use CloudFlare and don't mind the others.

    Sad.. bunny...
    https://www.wikihow.com/Tell-if-Your-Rabbit-Is-Lonely

  • @BunnySpeed said:
    Sad.. bunny...

    Oh... I can't see a sad bunny, it breaks my heart. :cry:

  • BunnySpeedBunnySpeed Member, Host Rep
    edited November 2019

    @ITLabs said:

    @BunnySpeed said:
    Sad.. bunny...

    Oh... I can't see a sad bunny, it breaks my heart. :cry:

    Thank you for the pats <3 Is much better now

    Thanked by 1ITLabs
  • jsgjsg Member, Resident Benchmarker

    Frankly, I think that the number rat race ("A is only x ms but B is y ms!") serves only one party -> the sellers/providers.

    The relevant point is how much faster YOUR SERVER is reachable. If it's e.g. 200 ms TTFP and CDN A brings it down to 40 ms while CDN B brings it down to 50 ms then both win you a whole lot!
    Add to that friendliness, support, flexibility, price and the fact that CloudF%$&# increasingly acts like a private NSA and regularly f_cks up and the answer is clear -> anyone except CF. And BunnyCDN has an excellent reputation for a reason!
    Case closed.

  • JordJord Moderator, Host Rep

    Just go full BunnyCDN and don't look back. BunnyCDN is prem. Full of features and new ones coming all the time. Plus it has a great team behind it. They will always take care of you.

    I couldn't recommend them enough!

  • edited November 2019

    I use paid cloudflare so people can't get to my WordPress real IP and DDoS that, also so I can put some custom filters on certain pages, that are always "under attack" (wp-admin for example).
    I also use a cdn.mydomain.com cname linked to BunnyCDN, so it serves css, js and everything else a lot faster.
    Adding a nice caching plugin for wp like wp-rocket is also a good idea.
    So for my use case - a mix of both CF+Bunny is ideal and has given me the best results, specially on a WordPress site.

    Thanked by 1uptime
  • BunnyCDN. Just 10 USD per year.

    If you want, you can try another free CDN, if you don't have so much traffic or you want to be always free

  • @jsg said:
    Frankly, I think that the number rat race ("A is only x ms but B is y ms!") serves only one party -> the sellers/providers.

    The relevant point is how much faster YOUR SERVER is reachable. If it's e.g. 200 ms TTFP and CDN A brings it down to 40 ms while CDN B brings it down to 50 ms then both win you a whole lot!
    Add to that friendliness, support, flexibility, price and the fact that CloudF%$&# increasingly acts like a private NSA and regularly f_cks up and the answer is clear -> anyone except CF. And BunnyCDN has an excellent reputation for a reason!
    Case closed.

    THIS.

    Seriously, for most use cases, CF free already accelerates and protects your site sufficiently. There are valid objections to CF which @jsg has pointed out but I really don't don't think the ROI using multiple CDNs justify the effort.

  • I use both. BunnyCDN is great for serving static content.

  • uptimeuptime Member
    edited November 2019

    seems like cloudflare emphasizes the DDoS protection features.

    Am I correct in my assessment that BunnyCDN POPs are in fact "protected" but since they are serving static content it doesn't make much sense to advertise or engineer much in the way of a complex festure set for DDoS protection?

    Reading a thread from a couple years ago, it was the case then that charges due to extra traffic from DDoS could be capped simply by setting a limit for a given region (after which point the content would not be served from POPs in that region).

    I'm guessing that's still how it works and @BunnySpeed and company are okay with having cloudflare and other DDoS protection "specialists" handle the trickier filtering needs when necessary.

    I'd be interested to get a clearer understanding of how this sort of separation of concerns (such as described by @t0ny0 - which actually seems pretty straightforward) might work in practice - especially if there's anything new or something I'm missing with regard to mitigation options provided by BunnyCDN

  • BunnySpeedBunnySpeed Member, Host Rep
    edited November 2019

    @uptime said:
    seems like cloudflare emphasizes the DDoS protection features.

    Am I correct in my assessment that BunnyCDN POPs are in fact "protected" but since they are serving static content it doesn't make much sense to advertise or engineer much in the way of a complex festure set for DDoS protection?

    Reading a thread from a couple years ago, it was the case then that charges due to extra traffic from DDoS could be capped simply by setting a limit for a given region (after which point the content would not be served from POPs in that region).

    I'm guessing that that's still the case and @BunnySpeed and company are okay with having Cloudflare or other DDoS protection specialists handle the trickier filtering needs when necessary.

    I'd be interested to get a clearer understanding of how this sort of seperation of concerns (such as described by @t0ny0 - which actually seems pretty straightforward) might work in practice - especially if there's anything new or something I'm missing with regard to mitigation options provided by BunnyCDN

    That is definitely about how we see it. Of course, there is a layer of protection that happens as well, but it's not something we focus on. We try to focus on very efficient delivery of static assets and most of our features are also geared towards that. This can go perfectly well hand in hand and actually a lot of our users use CloudFlare together with BunnyCDN. It can work really well.

    I think CloudFlare has grown so large that it has caused some confusion where a lot of people think that a CDN is necessarily some sort of overlay on top of your domain. They do that because they have a much broader system combining WAF, DNS, CDN and other features all into one package.

    As such, while I find the statement about using multiple condom brands very funny, technically it doesn't really make sense. We actively encourage users not to run BunnyCDN as the root or www of the domain unless required for the specific use-case or if setting up full site caching and most of our users deliver their static content via a subdomain. This means you are in fact not layering security and wrapping bunnies in a condom, but just using each system for its own part of the process.

    It does add a tiny overhead with the extra DNS request, but so does proxying your whole domain.

    I don't want to convince anyone that this is what they should do, but perhaps to clear up some confusion. There is a different topic of performance, but I don't want to go into that here due to many factors such as pricing, features, support, bias etc, so it would be unfair and pointless.

  • @BunnySpeed said:

    @uptime said:
    seems like cloudflare emphasizes the DDoS protection features.

    Am I correct in my assessment that BunnyCDN POPs are in fact "protected" but since they are serving static content it doesn't make much sense to advertise or engineer much in the way of a complex festure set for DDoS protection?

    Reading a thread from a couple years ago, it was the case then that charges due to extra traffic from DDoS could be capped simply by setting a limit for a given region (after which point the content would not be served from POPs in that region).

    I'm guessing that that's still the case and @BunnySpeed and company are okay with having Cloudflare or other DDoS protection specialists handle the trickier filtering needs when necessary.

    I'd be interested to get a clearer understanding of how this sort of seperation of concerns (such as described by @t0ny0 - which actually seems pretty straightforward) might work in practice - especially if there's anything new or something I'm missing with regard to mitigation options provided by BunnyCDN

    That is definitely about how we see it. Of course, there is a layer of protection that happens as well, but it's not something we focus on. We try to focus on very efficient delivery of static assets and most of our features are also geared towards that. This can go perfectly well hand in hand and actually a lot of our users use CloudFlare together with BunnyCDN. It can work really well.

    I think CloudFlare has grown so large that it has caused some confusion where a lot of people think that a CDN is necessarily some sort of overlay on top of your domain. They do that because they have a much broader system combining WAF, DNS, CDN and other features all into one package.

    As such, while I find the statement about using multiple condom brands very funny, technically it doesn't really make sense. We actively encourage users not to run BunnyCDN as the root or www of the domain unless required for the specific use-case or if setting up full site caching and most of our users deliver their static content via a subdomain. This means you are in fact not layering security and wrapping bunnies in a condom, but just using each system for its own part of the process.

    It does add a tiny overhead with the extra DNS request, but so does proxying your whole domain.

    I don't want to convince anyone that this is what they should do, but perhaps to clear up some confusion. There is a different topic of performance, but I don't want to go into that here due to many factors such as pricing, features, support, bias etc, so it would be unfair and pointless.

    Thank you! Btw have you set a webp pricing yet?

  • sanvitsanvit Member
    edited November 2019

    @Chievo said:

    @BunnySpeed said:

    @uptime said:
    seems like cloudflare emphasizes the DDoS protection features.

    Am I correct in my assessment that BunnyCDN POPs are in fact "protected" but since they are serving static content it doesn't make much sense to advertise or engineer much in the way of a complex festure set for DDoS protection?

    Reading a thread from a couple years ago, it was the case then that charges due to extra traffic from DDoS could be capped simply by setting a limit for a given region (after which point the content would not be served from POPs in that region).

    I'm guessing that that's still the case and @BunnySpeed and company are okay with having Cloudflare or other DDoS protection specialists handle the trickier filtering needs when necessary.

    I'd be interested to get a clearer understanding of how this sort of seperation of concerns (such as described by @t0ny0 - which actually seems pretty straightforward) might work in practice - especially if there's anything new or something I'm missing with regard to mitigation options provided by BunnyCDN

    That is definitely about how we see it. Of course, there is a layer of protection that happens as well, but it's not something we focus on. We try to focus on very efficient delivery of static assets and most of our features are also geared towards that. This can go perfectly well hand in hand and actually a lot of our users use CloudFlare together with BunnyCDN. It can work really well.

    I think CloudFlare has grown so large that it has caused some confusion where a lot of people think that a CDN is necessarily some sort of overlay on top of your domain. They do that because they have a much broader system combining WAF, DNS, CDN and other features all into one package.

    As such, while I find the statement about using multiple condom brands very funny, technically it doesn't really make sense. We actively encourage users not to run BunnyCDN as the root or www of the domain unless required for the specific use-case or if setting up full site caching and most of our users deliver their static content via a subdomain. This means you are in fact not layering security and wrapping bunnies in a condom, but just using each system for its own part of the process.

    It does add a tiny overhead with the extra DNS request, but so does proxying your whole domain.

    I don't want to convince anyone that this is what they should do, but perhaps to clear up some confusion. There is a different topic of performance, but I don't want to go into that here due to many factors such as pricing, features, support, bias etc, so it would be unfair and pointless.

    Thank you! Btw have you set a webp pricing yet?

    iirc it's $9.95/m if you let BunnyCDN do it for you, and free if you do it on your servers. That $9.95/m also includes manipulation engine, CSS/JS minify, etc.

    Thanked by 2Chievo uptime
  • vyas11vyas11 Member
    edited November 2019

    @sanvit said:

    @Chievo said:

    Thank you! Btw have you set a webp pricing yet?

    iirc it's $9.95/m if you let BunnyCDN do it for you, and free if you do it on your servers. That $9.95/m also includes manipulation engine, CSS/JS minify, etc.

    How does that compare with say a Cloudinary (I had tried the free plan some time back) or the other service I do not recall.

  • @vyas11 said:

    @sanvit said:

    @Chievo said:

    Thank you! Btw have you set a webp pricing yet?

    iirc it's $9.95/m if you let BunnyCDN do it for you, and free if you do it on your servers. That $9.95/m also includes manipulation engine, CSS/JS minify, etc.

    How does that compare with say a Cloudinary (I had tried the free plan some time back) or the other service I do not recall.

    I never used Cloudinary, but I guess the 'no limit and pay as you go' is better for me :)

  • @sanvit said:

    I never used Cloudinary, but I guess the 'no limit and pay as you go' is better for me :)

    They do have that- gets pretty pricey though. Loved their image manipulation on the fly feature. Publitio is the other one I was talking about. Funny I forgot considering that's a paid one for us.

Sign In or Register to comment.