Hi - James - that was the sort of stuff that I was interested in - I am amazed that Virgin manages to push out content with that amount of infrastructure... I always envisaged that you needed a lot of egg-frying server farms to deliver that amount of content. That said, I got quite a lot from the links that Jeremy and a few others pushed out the door. http://open.bbc.co.uk/labs/Labs%20Presentation%202006-7.ppt <http://open.bbc.co.uk/labs/Labs%20Presentation%202006-7.ppt> http://open.bbc.co.uk/labs/mark%20hewis%20presentation.ppt <http://open.bbc.co.uk/labs/mark%20hewis%20presentation.ppt> http://open.bbc.co.uk/labs/radio1_innovationlabs.ppt <http://open.bbc.co.uk/labs/radio1_innovationlabs.ppt> The "history" page definitely brought tears of nostalgia back to me! My general interest is in understanding (like I said - without giving away official secrets) - what sorts of infrastructure are needed to do what - what sorts of languages/frameworks/paradigms are prevalent, in containment, on the horizon, and why - etc, etc. What is the major driver for choosing/keeping/ditching languages/frameworks/paradigms - productivity, TTM, flexibility, ??? Thanks again - Derryck.
---------------------------------------- Derryck Lamptey, IT Specialist Infrastructure Technology Solutions - Directories TD Bank Financial Group Addr: Scarborough Operations Centre 740 Progress Ave, 3rd Floor Scarborough, ON, M1H 2X3 Desk: (416) 307 0124 Mobile: (416) 318 9701 Fax: (416) 983 4280 Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Group: [EMAIL PROTECTED] ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Cridland Sent: May 1, 2007 2:51 PM To: [email protected] Subject: Re: [backstage] The real backstage story? On 4/22/07, Lamptey, Derryck <[EMAIL PROTECTED]> wrote: RoR, spring, hibernate.... Dotnet, java, php, etc, etc. What is the real backstage story? I'd find it very informative for someone to give us non-BBC-backstagers (without violating what's left of the official secrets act) some sort of overview of how the (impressive) Beeb backstage infrastructure is put together. It would be interesting to hear in (episode 1) when it started, and what backstage technologies were used (episode 2) current infrastructure in the context of lessons learned, (episode x) future directions? I think that this would make a riveting series - the program director for "click online" might even get stuck in on this one! ...Lots of opportunities for us backstagers to engage in constructive and thought-provoking discussion... I am a newbie to the list, I hope that this is not a "RTFM" type of question!! Derryck, Not your question, but you might like to know how Virgin Radio's websites work (since I know about this a bit, whereas the BBC's infrastructure is totally unknown to me): We have two live Windows streaming servers, two for on-demand, plus a Helix box, and a Shoutcast/Icecast box (both servers run on the same hardware). Lots of encoders feeding in to these. We have around six live webservers, and do fun stuff with Squid for our "images" server (i.virginradio.co.uk). Our webservers are balanced using a BigIP box, rather than the elegant round-robin DNS that I believe others use. In addition, we have two webservers, a database mirror, and two WM streaming servers in NYC, and routers in most of the major internet hubs (Amsterdam, Manchester, London, Hong Kong, Frankfurt, NYC). The NYC servers are not just for load-balancing but also act as disaster-recovery boxes should anything happen to Golden Square, and act as spurious reasons for our technical services department to go out and "upgrade" them. We're fully multicast-enabled, and I believe on IPv6 too. In terms of the technology we use: our streaming software is Visual Basic wrapped around Windows Media Encoders: the VB inserts some additional metadata into the stream and also manages all our now-playing functionality. Otherwise virtually every bit of software is PHP, and homegrown - our content management system, all the webstuff we've written, the lot. Key learnings are to minimise live database lookups, and remove them entirely on our high-traffic pages - replacing them with regular cron jobs that output easy-to-parse text files. Other key learnings are writing "widgets" - small, reusable, pieces of code for use throughout our website network - rather than hulking great bits of code. We stopped using a content-delivery-network for things like images, when we realised that some work with Squid would make that easier to bring back in-house, but we definitely benefit from leaving the simple, static, stuff to be served by simple server instances. We use PHP mainly for ease of finding great developers and designers, but also to be able to use open-source material. We will be contributing back - indeed, our version of the BBC Backstage website goes live very shortly, which will debut with a small and easy-to-use JavaScript animation tool. Our network is nowhere near as complex as the BBC's; but I hope that's a useful start and there's some useful info in here. -- http://james.cridland.net/ ******************** NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous nêtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation dune partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement lexpéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
