Architecting for Scalable and Usable Web Applications As Enterprises and Software Vendors start to develop more and more applications on the Internet there is an increasing importance to architect these applications for both growth and for the optimal user experience. Software + Services allows you to develop fantastic applications, but there are pitfalls with architecting the applications in the wrong way. Our Central Region Architect Evangelists will lead us through two great discussions on scaling web applications and creating the best possible user experience. Session 1: Architecting for Scalable Web Applications In this session we will explore the patterns that typical applications follow as their scalability needs grow due to increased demand. We will also discuss best practices from companies that have gone up the scalability curve like Amazon.com, MySpace and Flickr. We will discuss the common bottlenecks that prevent scalability as well as how to tackle tough issues like state management in a application that is scaled across servers and even data centers. We will also discuss the “scale later” philosophy and how it should be accompanied by a solid plan to scale your applications. Session 2: Architecting for Usable Web Applications In this session we will discuss how to architect your application with the user in mind. We have more choices than ever before for developing applications (Traditional Web Apps, AJAX, RIA technologies like Flex and Microsoft Silverlight and even smart clients) and picking the technology is only part of the solution. The architecture of the application must be designed correctly to provide a pleasing user experience and (potentially) to add new and interesting clients in the future.

1. ArcReady: Architecting for Scalable and Usable Web Applications

3. SESSION 1: Architecting for Scalable Web Applications

4. So you have a scalability problem? Congratulations!

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

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

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.