|
|
|
|
|
by jt2190
39 days ago
|
|
> [L]eadership thinks (likely correctly) that implementing them would just hurt company’s bottom line. Exactly. There's little "win" here for the business, especially when the simpler "just cap at n requests" solution exists. Pursuing this solution: - introduces more technical complexity (increased cost of developing, testing and maintentance) - forces overage costs onto the vendor, who will then... increase prices to cover these costs, which upsets customers and makes the company less competitive. - doesn't improve cost prediction (since n requests can be costed out a $/request quite easily and reliably) (The cynical will say something about "the business has an incentive to _not_ fix this issue because they get paid for overages", but this assumes that Cloudflare has the, "monopolistic" market power to make customers unhappy and still charge whatever they want. In this case implementing billing caps wouldn't do anything because Cloudflare could just... charge whatever they want.) |
|