[silvestrov]

> Developers always want to try the new flashy things [...] On the other hand, management mostly sees risks .. mostly wants new fancy features

I have the inverse experience: management wants to brag about tech and therefore force ill-suited tech onto the developers.

I've had managers that wants a CDN because that's what all professionals do and they don't take a moment to think about added risk by adding more components to the system (or even if it adds any benefit at all).

[wcarss]

CDNs are a great example where, if you don't have the problem they solve yet, using them correctly might not be worth your time.

You may now have separate asset domains, interactions of cache expiry headers across different servers, custom header forwarding through your front-ends, new separate asset packaging and deployment steps during shipping, and a slew of other "new stuff" to think about during every deploy, that can all break, and that you ought to have multiple people on the team really understand to use properly, or to debug if it's not working.

If you have <100 users, growing to ~500 by the year's end, you maybe don't need to spend time on any of that stuff yet.

[zinekeller]

> I've had managers that wants a CDN

I'm hoping that the purported CDN is not for an internal, company-only application.