Web Oriented Architecture

Un document d’IBM avec quelques éléments interessants dont cette conclusion :

For the class of Web applications that I call immersive Web applications, well-designed Ajax/REST applications are far superior to traditional server-wide Web applications with regard to user experience, responsiveness, and scalability. However, an architectural style’s run-time characteristics aren’t the only determinant of success for a software project and Web application. There are some tough non-run-time problems with creating Ajax/REST applications, including determining how to adopt Ajax for your application (if at all), problems of large-scale JavaScript development, cultural issues, and packaging problems. In Part 2, I’ll discuss different adoption options and organizational considerations to improve your chances for success with Ajax.

Il serait interessant que cette conclusion remonte a tous les auteurs de frameworks, patterns, … y compris chez IBM !

Certains se demandent comment est architecturé un site comme myspace, la réponse est ici :

http://www.eweek.com/article2/0,1895,1947684,00.asp

au dela des chiffres il y a un phénomene interessant, le changement rapide d’architecture. C’est a peu près la même chose pour Amazon.
Coté infrastructure on voit bien qu’il y a un interet a disposer d’infrastructures capables de croitre a l’infini et de profiter des avancées technologiques facilement.

Le grand récupérateur (IBM) parle de Web

Je retiens parmis de nombreux points :

The Next Rev of the Web Programming Model (Source: IBM)

• Rich Internet Applications (Ajax, Flash, etc.)
• Instant Web apps (minutes instad of hours and days)
• Lightweight programming models
• Mashable assets (new — and just as importantly, existing IT resources (Ross Mayfield) made to work in this new situational model)
• Feeds