Cloudflare Alternatives

What are some alternatives to cloudflare for CDN, DDOS Protection, and DNS management. I am planning to create a website and it seems cloudflare is a great one but I know there shadiness and I know that cloudflare is just one big MITM.

I'm not certain this topic warrants a thread. I have a static website, and trust me when I write that it's very unlikely anyone will DDoS it. No one is going to care. People write about getting slashdotted and other things, but only disgustingly unoptimized websites are taken down like that nowadays, and it's again very unlikely anyone is going to care for at least the first several years it exists.

>>13906 This very much depends on the content and purpose of your website. For example there exists a cottage industry of systematic DDoS/extortion attacks for websites related to cryptocurrency.

>>13906 Let's just say "Enterprise" related.

>>13905 First of all, you don't need to wage slave "FUD". Lainons (mostly) don't like or trust cloudflare in the first place. Second of all, >DDOS protection You don't need this. >CDN Marketing made you think you need this. >DNS management dnsmasq, BIND, TinyDNS, etc., etc., etc.

>>13909 Why should I not need a CDN management?

>>13916 Because you aren't global and the soykaf loads fine.

https://en.wikipedia.org/wiki/Eucalyptus_(software) https://en.wikipedia.org/wiki/Globus_Toolkit https://en.wikipedia.org/wiki/OpenNebula i hope that i'm helped

>>13916 >Why should I not need a CDN management? You probably don't need it unless you have a site that simultaneously: 1. Hits reddit's front page. 2. Is loaded with multiple MB of javascript and/or "hero image" soykaf. Keep javascript to a minimum (or ideally absent) and keep all images as small thumbnails. You're welcome.

>>15480 https://solar.lowtechmagazine.com/ has also shown some interesting results on energy, bandwidth and CPU use by the dithering of larger images.

>>15480 But I'm planning to create my own E-commerce business.

>>15480 I don't like small images, I like them RAW!

>>15513 unprotected, un-copyrighted, un-watermarked, public domain, and RAW. banks hate this simple yet effective image sharing trick.

>>15481 This webshitter's original blog is hosted on such an abhorrent webshit CDN (Typepad) that requires tons of javascript and RSBL pass to even load, and half the images are not even retrievable anymore. What a hypocrite. Besides, most old articles lose their meaning when each image, especially graphs are reduced to monochrome dithered hipster nonsense. Instead of being such a virtue signalling soynigger, he could have just hosted the whole thing at home on more powerful computer with faster internet connection and grid electricity. After all, CDN webshit and BeagleBone smolwebshit consume more energy combined.

there's no silver bullet for serving lots of users at once and mitigating ddos attacks. cdn services like cloudflare, akamai, etc. work simply because they have a ton of cache servers all over the world, which allows them to just soak up traffic. however, you probably don't actually need this kind of capacity if you just minimize the number of things your server needs to host and avoid dynamic content whenever possible. a cheap vps + lighttpd + a static site generator with minimal images will be robust enough for most personal websites. now, if you for some reason need to host a lot of big files, video or music for instance, then you may begin to run into capacity issues even if your site isn't super popular. in this case, you might consider hosting these on some sort of cdn. if, on the other hand, you need to host dynamic content (because you're making a social media site or something) then capacity isn't actually the issue. since your content isn't cacheable, a cdn won't keep your server from being overwhelmed by your regular users. the only solution here is to expand your infrastructure as needed, or just accept that certain parts of your site will sometimes be slow. for abusive traffic, you can just host most of the same mitigations a cdn will give you yourself. put big files and computationally expensive api calls behind a captcha, implement an automated spam filter, require accounts for certain things, ... and so on. the choice you make here will depend on a number of factors which are specific to your site, but suffice to say you can get pretty far without a cdn.