Read the Original Article at http://www.informationweek.com/news/showArticle.jhtml?articleID=202102624
Consumer technology has raced so far ahead of the enterprise that people used to blogs, mashups, and Ajax apps on the Web can feel like they've stepped through a time warp when they face circa 1990s technologies at work. Companies need to adapt, but wisely--not all Web 2.0 technologies are useful in business.
The Web 2.0 label covers a variety of tools, all aimed at helping people communicate and collaborate more efficiently. Most companies will focus on mashups, which mix data from internal and external sources in new ways. Some are simply innovative ways of presenting information, but the most advanced are full-blown apps, with many vendors promoting development platforms aimed at staff without programming experience.
Other Web 2.0 tools are best kept within an organization's borders. For example, setting up shop in Second Life will be a waste for most businesses, but virtual environments can be useful as a way to host internal meetings, allowing more interaction than voice alone at a lower cost than videoconferencing. The same goes for wikis, which act as straightforward but powerful knowledge management systems.
Web 2.0 means replacing static Web sites with Web services that are accessed through browser-based clients. Every company that aspires to interactivity on the Web needs to evaluate Web 2.0's underlying technologies. Rich Internet apps make most sense in frequently updated parts of sites and areas that require user input.
Ajax, because of its widespread browser support, remains the standard for RIAs. Internal apps that run on IT-controlled platforms can also use Java SE, Curl, Adobe Flex, or Microsoft Silverlight, which are more capable but require plug-ins and may limit choice of browser or operating system. Attempts by Adobe and Google to take RIAs beyond the browser are still immature.
Businesses that already use Web services have an advantage, though a service-oriented architecture alone isn't enough to support RIAs. The bloated XML standards would choke lightweight Ajax apps, leaving their supporting Web services to use ad hoc data formats.
New hardware also may be needed. Well-designed RIAs don't transfer any more data than static Web pages, but they break it into smaller chunks, hammering servers with multiple TCP connections that may transfer just a few bytes each. Dealing with these can require infrastructure upgrades. And servers that host mashup components for the Web need to be able to cope with surges in demand, which virtualization can help.