Take a look at KinkLive.com. We were the first porn company to do live streaming in HD using a CDN (Bitgravity), all paid for, by the minute, with a micro currency system (kinks) that we built.
I've posted about small parts of it in various places, but not the whole experience. I no longer work there (since April 2010), so while I know they still use quite a bit of the serving infrastructure that I built, my knowledge is now quite a bit out of date.
One fun bit that I built is called the cockblocker (as you can imagine, we used all sorts of fun names for internal projects). People who repeatedly attempt to hack the system (usually through various forms of abuse like failed login attempts) would automatically get their IP address routed to /dev/null.
Comments
The article suggests that this is for live streaming shows. Would a CDN based approach work in this use case?
Take a look at KinkLive.com. We were the first porn company to do live streaming in HD using a CDN (Bitgravity), all paid for, by the minute, with a micro currency system (kinks) that we built.
Very interesting! Thanks for your reply. Have you ever posted or discussed your infrastructure before?
I've posted about small parts of it in various places, but not the whole experience. I no longer work there (since April 2010), so while I know they still use quite a bit of the serving infrastructure that I built, my knowledge is now quite a bit out of date.
One fun bit that I built is called the cockblocker (as you can imagine, we used all sorts of fun names for internal projects). People who repeatedly attempt to hack the system (usually through various forms of abuse like failed login attempts) would automatically get their IP address routed to /dev/null.