Like any new web technology there is sometimes the misconception that it can be used and implemented within the enterprise the same as with public consumer web applications. This is natural because these consumer-facing applications often are constrained the way enterprises are and can act on new technologies and approaches faster. This is true with Ajax.
Think of a car analogy. If you put a fancy Ferrari body on top of a Pinto frame and engine what do you have? From a distance you can say you have a Ferrari but to those who have to get up-close, interact with, and maybe even drive it; its still run’s like a Pinto.
Now consider enterprise web applications. With the coming out party of open-source Ajax widgets enterprises believe that by ‘bolting’ some of these free snippets (little Ajax eye candy pieces to make a site look and feel better to the user) onto existing apps is all that is needed to say “Yes, we’re doing Ajax.” But think about it. All that is being done is similar to the scenario above whether business managers realize it or not. If they don’t, they are really getting shortchanged on the business activity optimizing gains from Enterprise Ajax.
To garner the full benefits, enterprises need to carefully calculate how to implement an Ajax enterprise strategy that not only provides the basic improved user experience but can enhance the entire set of capabilities as well. Enterprise Ajax is in fact an architectural strategy so as to marry the best of what Ajax has to offer with enterprise architectures such as SOA while making sure that security, scalability, reliability and governance are correctly taken care of. Enterprise Ajax enables enterprises to leverage the best of Rich Internet Applications and Service-Oriented enterprise Applications with the specific goal of optimizing any and all business operations of an enterprise while guarding access by authorized people to the correct information assets and ensuring delivery and proper execution.