1. This is the demo I made for the Microsoft Demos Happen Here competition. The criteria was that it had to be under 10 minutes, and show one or more of the features from the launch wave technologies - Visual Studio 2008, SQL Server 2008 and Windows Server 2008.

    I chose to demonstrate PHP running on IIS7 using FastCGI, then integrating this with an ASP.NET application before finally load balancing the whole application between two servers in a high availability, automatic failover cluster.

    I managed to do all that with 2 minutes to spare, so I think it's pretty clear that Windows Server 2008 is the best web stack in the world.

    # vimeo.com/1439786 Uploaded 684 Plays 0 Comments
  2. This year, a small team of developers delivered a ASP.NET MVC app, with a Neo4j backed, all running in Azure. This isn't in POC; it's a production system. Also, unlike most graph DB talks, it's not a social network!
    In this session you'll hear the stories of:
    - what our project is, why we chose a graph db, how we modelled it to start with and how our model was wrong
    - how we deploy neo4j in Azure
    - how we diagnosed and fixed a performance problem that spanned the CLR, the JVM and Azure
    - how we built our own Neo4j client for .NET, complete with a fluent interface and internal logic to serialize .NET - expressions into Groovy comparisons (It was only slightly scary.)

    # vimeo.com/43676873 Uploaded 3,941 Plays 0 Comments
  3. A tiny subset of your users can’t login: they get no error message yet have both cookies and JavaScript enabled. They’ve phoned up to report the problem and aren’t capable of getting a Fiddler trace. You’re serving a million hits a day. How do you trace their requests and determine the problem without drowning in logs?

    Marketing have requested that the new site section your team has built goes live at the same time as a radio campaign kicks off. This needs to happen simultaneously across all 40 front-end web servers, and you don’t want to break your regular deployment cadence while the campaign gets perpetually delayed. How do you do it?

    Users are experiencing 500 errors for a few underlying reasons, some with workarounds and some without. The customer service call centre need to be able to rapidly triage incoming calls and provide the appropriate workaround where possible, without displaying sensitive exception detail to end users or requiring synchronous logging. At the same time, your team needs to prioritize which bugs to fix first. What’s the right balance of logging, error numbers and correlations ids?

    These are all real scenarios that Tatham Oddie and his fellow consultants have solved on large scale, public websites. The lessons though are applicable to websites of all sizes and audiences.

    The talk will be divided between each of the three scenarios described here, and then stuffed full of other tidbits of information throughout.

    # vimeo.com/43624434 Uploaded 685 Plays 0 Comments
  4. Presented in Manila, Philippines on Wed 12th Dec 2012.

    Big websites fail in spectacular ways. In this session, five-time awarded ASP.NET/IIS MVP and ASP Insider Tatham Oddie will share the problems that he and fellow Readify consultants have solved on large scale, public websites. The lessons are applicable to websites of all sizes and audiences, and also include some funny stories. (Not so funny at the time.)

    A tiny subset of your users can’t login: they get no error message yet have both cookies and JavaScript enabled. They’ve phoned up to report the problem and aren’t capable of getting a Fiddler trace. You’re serving a million hits a day. How do you trace their requests and determine the problem without drowning in logs?

    Marketing have requested that the new site section your team has built goes live at the same time as a radio campaign kicks off. This needs to happen simultaneously across all 40 front-end web servers, and you don’t want to break your regular deployment cycle while the marketing campaign gets perpetually delayed. How do you do it?

    Users are experiencing HTTP 500 responses for a few underlying reasons, some with workarounds and some without. The customer service call centre need to be able to rapidly evaluate incoming calls and provide the appropriate workaround where possible, without displaying sensitive exception detail to end users. At the same time, your team needs to prioritize which bugs to fix first. What’s the right balance of logging, error numbers and correlations ids?

    Your application is running slow in production, causing major delays for all users. You don’t have any tools on the production servers, and aren’t allowed to install any. How do you get to the root of the problem?

    # vimeo.com/55578267 Uploaded 448 Plays 0 Comments

Tatham's Presenations

Tatham Oddie Plus

Presentations by Tatham Oddie

Browse This Channel

Shout Box

Heads up: the shoutbox will be retiring soon. It’s tired of working, and can’t wait to relax. You can still send a message to the channel owner, though!

Channels are a simple, beautiful way to showcase and watch videos. Browse more Channels.