Within Sun we have an organisation called ISV-Engineering. One of the things they do is work with partners to get partner products working as well as possible on Sun and interacting with communities to achieve the same result with them. This means that they have a wealth of real world and up to date experience in architectures that really work. In constructing Web 2.0 applications, design choices ultimately impact the systemic qualities of performance, scalability, availability, extensibility, interoperability, and security. In implementing a SAMP architecture, the intent of these choices is to improve the user experience by making architectural decisions that work, for the long term.
Two of my colleagues, Amanda Waite and Marina Fisher, have just published a blueprint Addressing Systemic Qualities in SAMP Architectures which directly addresses these issues and provides advice on how to effectively architect a solution. So if this is something you are working on the blueprint is freely available and if you have any questions on the blueprint why not raise them via the Web 2.0 Technology Partners forum and we'll make sure they are answered.
If you found this blueprint interesting, there is an extensive collection of other blueprints available, as well as a collection of resources on the Sun Partner Advantage Web Community site.
why company not want to use web 2.0
Posted by dushkui on May 25, 2009 at 04:30 AM GMT #