Question

I know this seems like a really subjective question, but from what I’m reading, I’m generally confused. We are developing a web-based application that has tabbed windows, etc-very much a “desktop-like” application graphically. About half the page never or rarely changes, and the other half is content that could be handled dynamically within a main window.

So from the ajax proponents, this seems like a perfect example of something that would benefit from ajax. The only thing stopping me (other than lack of ability :-D) is that I’m concerned we would degrade the speed of the app (which isn’t really all that great anyway…)

Can anyone either shed some light on this subject or point me to more reading material on performance differences when changing lots of data at once via ajax?

Answer 1

About the differences that can often be seen :

• If you load more data via AJax requests, and less via “full-page” requests, it means :
  • less data will go through the network (only content of pages, not menus, sidebars, …)
  • less thins to generate on the PHP/SQL side (same : no menu, …)
• But more Ajax requests can also mean more requests, depending on how your application is developped
  • Which can mean more load on the server…

You also might want to think about :

• Indexation by search engines,
• Accessibility,
• Graceful degration,
• and all the possible stuff like that…

Which, in the end, can mean you’ll maybe spend lots of additionnal time developping the “more Ajax” version ; and time is money — and a few days of developper-time can cost more than renting/buying a second server.

In the end, I would say what really matter is not “performance” : you’ll probably have greater gains spending a couple of days optimizing what you already have (profiling on the backend side, minifying/compressing JS/CSS, merging JS/CSS files to have less HTTP requests, …) than by transforming everything to “full-Ajax”.

And, of course, what really matters is user-experience !