Depends on your use case.

If you have a very inefficient backend (maybe legacy project?), you have massive amount of traffic (say 100K req/s or above) or you really must have sub-500ms latency absolutely everywhere in the world, then it might make sense to slap a CDN (or similar) on top of that.

In pretty much any case outside of that, it makes no sense to waste the time, money or effort on CDNs. But, all the CDN companies seemingly have convinced half the internet that you absolutely must use a CDN, otherwise you'll get hacked/broke/killed/sent to the moon, and they've been successful with this campaign too seemingly.

▲

esseph an hour ago | parent [-]

Data scraping.

If anything else, the AI machine wants near constant streams of new data, even if it already checked with you 30ms ago.

A CDN helps immensely.

Also keeps you from getting DDoS'd if you did something like run it off your home connection.

	▲	embedding-shape an hour ago \| parent [-]
		Your webserver most likely have "rate limiting" built in already, which you can configure to act based on lots of variables typically. Set a limit of 1 req/s or whatever, and you've stopped 99% of all DDoS you'll encounter on the public web. If your visitors get cranky, up it to 10 req/s and you still are preventing most of the "abusive traffic", granted your backend/website isn't completely upside down when it comes to performance and resource usage. CDN is something you do once you run out of options, not something you should reach for immediately, it makes no sense in most cases of just hosting a website.