The document outlines a workshop agenda focusing on architecting scalable and usable web applications, with sessions dedicated to scalability issues and best practices for usability design. It discusses concepts such as performance, load vs stress, and various architectural patterns and anti-patterns for application development. The document emphasizes the importance of user experience and design principles in building effective applications.

1. ArcReady: Architecting for Scalable and Usable Web Applications

2. Agenda SESSION 1: Architecting for Scalable Web Applications 15 Min Break SESSION 2: Architecting for Usable Web Applications Evals & Raffle

3. SESSION 1: Architecting for Scalable Web Applications

4. So you have a scalability problem? Congratulations!

5. References “ Running a megasite on Microsoft Technologies” (MIX06) “ Myspace.com: Megasite V2” (MIX07) “ Amazon.com's Simple Storage Service, Elastic Compute Cloud, and Simple Queue Service” (SAF07) “ Building Scalable Web Sites” Book by Cal Henderson – Flickr architect

6. Scalability <> Performance

7. Scalability is how your application behaves as the number of users increases

8. Performance is how your application behaves when there is just one user

9. Number of Requests Cost per Request

10. Load <> Stress

11. Load is how many simultaneous users your application can serve

12. Stress is how well your application behaves when resources become limited

13. Where are the scalability limits? Network Database Web server Code

14. Pattern: Nickel Defense

15. Pattern: Scale Up

16. CASE STUDY: Scaling up with IIS7 at Dell.com

17. Simplified server management Fewer servers, reduced costs Improved performance Deploy Windows Server ® 2008 Enterprise operating system with Internet Information Services 7.0 Implement fully automated server and application deployment Simplify management of servers that run Dell.com Reduce number of servers and rate of server growth Improve site performance to maintain good user experience Dell simplifies server management, lowers costs, and increases Dell.com Performance “ Our vision for the Dell.com architecture absolutely requires the new features in Windows Server 2008, which is key to our ability to simplify our online commerce environment.” Ben May, Senior Systems Engineer, Dell

18. PATTERN: Scale Out

19. PATTERN: Specialize Web Services Image Server Web Application

20. PATTERN: Split the application msdn.microsoft.com technet.microsoft.com microsoft.com

21. PATTERN: Split the database 1 Reference Transaction

22. PATTERN: Split the database 2 Write Copy Read Copy Read Copy

23. PATTERN: Geo Distribution

24. PATTERN: Offload the work

25. Anti-patterns Spending all your time looking at the code Caching everything (twice!) Services calling services (especially across the network)

26. DEMO: Team System Load Testing

27. Discussion: “Scale Later”

28. BREAK: 15 Minutes

29. SESSION 2: Architecting for Usable Web Applications

30. PART 1: What’s the Secret Formula?

31. What’s your favorite application?

32. What application do you use the most ?

33. Effective Satisfying Efficient Useful Adaptive Reliable Cost-effective Desirable Usable

34. Experience Engineering User Needs Interaction Design Information Design Visual Design Experiences that create value! + + +

35. PART 2: What is our palette?

36. Application Archetypes Information / Reference E-Commerce Data Viewer/Editor Utility Entertainment Document Viewer/Editor

37. UX Continuum SharePoint ASP.NET+AJAX Gadgets RIAs Infopath OBA Winforms WPF XNA Ubiquity Richness Next Generation

38. SharePoint Sites

39. Standards Based Web Apps (ASP.NET + AJAX & Mashups)

40. Gadgets

41. Rich Internet Applications (Silverlight)

42. Infopath Forms

43. Office Business Applications

44. Standards Based Windows Applications (Winforms)

45. WPF Applications

46. XNA Applications

47. DEMO: UX IQ

48. PART 3: Best Practices

49. Form follows function

50. Create a set of design tenets

51. Use the appropriate level of fidelity

52. DEMO: ProtoXAML

53. Build with the customer and user’s input

54. Build for ease of use ..but don’t forget the power users 70 20 10

55. Plan for concurrency

56. Balance the computing load

57. Balance security with usability

58. Build for supportability & maintenance

59. What are some of your best practices?

60. © 2008 microsoft corporation. all rights reserved. this presentation is for informational purposes only. microsoft makes no warranties, express or implied, in this summary.