Insights from Interop 2006
In my last post I promised that if I get any new insights worth sharing this week while I'm at Interop 2006, I'll write about them. Well, here's the first installment, which consistes of just three items. I'm supposed to be at the Keynote booth on the show floor soon, so this will be short, because it's quite a hike to get there.
I'm staying at the Luxor, a hotel cleverly designed to resemble an Egyptian pyramid. Egyptian motifs abound. To reach the Conference Center in the Mandalay Bay hotel, which is next door, you can take a cab, a shuttle bus, or ride on a tram. But I usually walk. I hike about half a mile through a network of corridors cleverly disguised as places to spend money -- two casinos, a shopping mall, theaters and entertainment centers, restaurants, etc. I know I need to exercise more, so this a token effort.
Back to the insights. Yesterday afternoon I attended the Application Performance Day. Peter Sevcik of NetForecast presented a very thorough analysis of Performance Improvement Solutions, covering QoS, Compression, CDN's and other Acceleration technologies. He also provided a sheet of references, some of which I will publish when I have more time. Two insightful comments I wrote down were:
- Fast delivery of sites results in slow delivery of pages. We all know that when the development process does not include time to think about performance, the results are not optimal. I thought Peter's simple rule captured this issue in a memorable way.
- Most developers build applications in a LAN-based environment, and don't insert a WAN simulator to test their performance. Another well-known problem nicely summarized. If you don't actually test your application in the production environment, or something that resembles it, you will surely run into performance problems in the real world.
Now I'm not sure what lessons (if any) I should draw from this dream. It certainly seems to be a metaphor for many of the discussions going on here about how to deliver large payloads to remote destinations via less than ideal routes! Maybe John Chambers actually offered some more concrete suggestions during his Interop keynote speech this morning; I was still in my hotel room moving the piano at that time.
Now I'm going to mingle with the crowds and find out if Interop can make me smarter today.