Case Study of Bungie.Net

nmb3000 writes "MSDN recently put up a case study of Bungie.Net (much more detailed than a previous one), the homepage for the creators of the Halo series, and its transition from Perl to .NET and ASP. From the study: 'The Bungie.net site is the online companion to the wildly successful Halo 2 video game for Xbox, released in November 2004 by Microsoft. The site also acts as the community hub for all things related to Bungie games. Built with the Microsoft .NET Framework, Bungie.net serves up more than 4 million pages per day, accumulating 300 gigabytes of online game statistics per month from more than 1 million games played daily.' This is an interesting look into the creation and integration of the very large and interactive website which was voted 'Most Innovative Design' by IGN Entertainment in 2004."

Comments

That's nice

[Trepalium]

How about we do a study on the gotdotnet workspaces, and how much better sourceforge is in terms of reliability, availablity and usability? How many sites have moved to SF because Microsoft's version were far too unreliable? Why do you suppose that all of Microsoft's "Open Source" projects (WiX, FlexWiki, etc) are located on sourceforge instead of gotdotnet?

Let's be honest. Although the insinuation within the case study is that perl was not capable of handling the task of getting so much traffic, and ASP.NET intrinsically is, this is clearly false. They could've rearchetected the website to cache content better, and perform better, but instead the decision was made to use the website as a showcase of ASP.NET technologies. There's nothing wrong with that, but we should not pretend that it's something that it's not.

Still Perl?

[Winterblink]

Description: Focused on the reimplementation of most of the existing Perl based site on the .NET Framework. Some features, however, were left as Perl implementations.

I'm curious, which features, and why? And are they still Perl, or have they been subsequently ported to .NET? If not, why not?