Is IT worth the wait?
thartric 120000G744 Comments (5) Visits (2318)
In most cases it probably depends on whether you are "just browsing" or "need it yesterday".
To stop and think about the round trip that a click of a mouse launches is something most of us don't spend much time with... unless we feel it is not worth the wait.
With IBM developerWorks, the user's request initially travels to a hosting center in the Northeastern US through a firewall. The request is dispatched via a load-balancer (NetDispatch/WTE) thru another firewall into the developerWorks server cluster. If the user signs into the site, that authentication is done thru Web Identity in one of several locations across the US. Then depending on the type of request, it gets served up on the user's glass by the appropriate combination of web application and database servers.
During this round trip, the response time a user experiences is influenced by a combination of IT aspects such as network infrastructure, system infrastructure, middleware, and web applications. My main objective in running the developerWorks site is 1) availability and 2) response time (among other items like security, accessible, usable, and more). In addition to ensuring the site remains available during spikes in activity or weekday maintenance, we are continually working to monitor and improve end user response time.
A good introductory article on building the components of a highly available J2EE platform can be found here
Our goal for loading a developerWorks page is Worldwide average response time of 5 seconds or less, and more often than not on a weekly basis we make that goal. We do find that US and Europe geographies usually come in lower than that average, while AP geographies come in higher.
... so lets have a lively conversation here... is it worth the wait? what is your response time experience like on developerWorks?