Mini-guide: Explaining CDN to clients who think it's a backup

Explaining CDN to clients who think it's a backup

Had a call yesterday with a client who INSISTED their CDN "wasn't working" because they deleted their origin server and the site went down. Here's how that went:

CLIENT: "I bought the CDN package from you for redundancy."
ME: "It's for speed, not backup. It caches content at edge nodes."
CLIENT: "So it's a copy of my website. That's backup."
ME: "It expires. If your server goes down, the cache clears, then 404."
CLIENT: "Then what did I pay for??"

I tried the "pizza shop" analogy — main kitchen is origin, CDN is having fridges at customer's houses with slices ready. They asked why their fridge was empty when the shop burned down. Fair point actually

Anyone got better ones? I'm collecting scripts for the next sales call disaster.

SNAPPED UP a RackNerd edge package last year, $12/YR ARE YOU KIDDING, but explaining it never gets easier.

I run 52 boxes across 8 providers and I STILL get this weekly

My go-to now:

• Backup = your spare tire in trunk
• CDN = building gas stations every mile so you don't drive to refinery
• Origin still needs to exist = refinery still needs to exist

But honestly? $/GB/RAM on CDN vs actual backup storage, clients see "distributed" and think "redundant." The word "distributed" is poison.

Had one guy ask why his "distributed backup" cost less than Veeam. Because it's NOT BACKUP HANK.

Xixixi I am try yesterday lah

"cdn is like you have many photo copy machine in many office, but you still need the original document in headquarters. I you burn headquarters, all photo copy become blank paper after some day"

Client am ask "then I need two headquarters?" xixixi

Very confused but very polite