I am about to finally release FANS.FM (murphy willing of course). 

Last week I thought about the static and dynamic concerns of FANS.FM and realized something big: this system was largely static. All public listener facing assets could be static files. The permalink for a broadcast, the player and the embed script could all be precomputed. 

I can host the majority of the traffic that FANS.FM will experience directly out of Amazon S3. Translation: I don't have to worry about it.  

Embeds will load quick and not slow your site down. More importantly: a mistake on my part in the dynamic web application can't affect your broadcast files. 

FANS.FM will be a more reliable and robust system running because large parts of it are statically compiled and served out of S3. Another translation: I will be able to sleep better at night. 

The true dynamic need for the system is in creating and managing the live broadcast. The host needs to interact with a live interface to manage the broadcast and incoming callers. This will represent a very small percentage of the traffic FANS.FM will receive. 

I recommend evaluating your static and dynamic concerns. If there is a static way to solve a problem then you have found your solution.