The document discusses architectural trends for modern distributed applications including service oriented architecture, software as a service, web 2.0, and cloud computing. It provides examples of how different application components map to architectural blueprints and outlines challenges around identity, data, and management in distributed architectures. Finally, it proposes next steps for using the blueprints to decompose existing applications, involving the right stakeholders, understanding technology mappings, and documenting repeatable patterns.

1. Architecting Modern Distributed ApplicationsClint EdmonsonArchitect EvangelistMicrosoftEmail: clinted@microsoft.comWeb: http://www.notsotrivial.netTwitter: @clinted

2. Industry Trends

3. Industry TrendsTrend 1: Service Oriented Architecture (SOA)

4. Industry Trends

5. Industry TrendsTrend 2: Software as a Service (SaaS)

6. Industry Trends

7. Industry TrendsTrend 3: Web 2.0

8. Industry Trends

9. Industry TrendsTrend 4: Rich Internet Applications (RIA)

10. Industry Trends

11. Industry TrendsTrend 5: Cloud Computing

12. Industry Trends

13. Industry TrendsSOA: Service Oriented Architecture RIA: Rich Internet ApplicationsInterop, Reuse and AgilityUser ExperienceSoftware + ServicesWeb 2.0SaaS: Software as a Service SocialNetwork EffectFlexible pricing and deliveryCloud ComputingService Utility & Scale

14. Heads in the Cloud, Feet on the Ground

15. Heads in the Cloud, Feet on the GroundWhen it comes to running applications, organizations today face a tension between control and economy of scaleControlHighLowEconomy of ScaleLowHigh

16. Application runs on-premiseBuy my own hardware, and manage my own data centerHeads in the Cloud, Feet on the GroundApplication runs at a hosterPay someone to host my application using hardware that I specifyApplication runs using cloud platformPay someone to host my application without specifying the hardware (they promise to be “infinitely” scalable)Application is supplied by a vendorPay for someone’s hosted application. Don’t care about the hardware, as long as it works. ControlHighLowEconomy of ScaleLowHigh

17. Heads in the Cloud, Feet on the GroundBuyBuild vs. BuyTension between build vs. buyBuild

18. “Packaged”ApplicationAn application that I buy “off the shelf” and run myselfHeads in the Cloud, Feet on the GroundHosted “Packaged”An application that I buy “off the shelf” and then run at a hoster“Packaged”using cloud An application that I buy “off the shelf”, that is hosted using cloud platform“Software as a Service”A hosted application that I buy from a vendorBuyBuild vs. Buy“Home Built”ApplicationAn application that I develop and run myselfHosted “Home Built”An application that I develop myself, but run at a hoster“Home Built”using cloud An application that I develop myself, that is hosted using cloud platform“Platform as a Service”A vendor hosted development and runtime environmentBuild

19. “Packaged”ApplicationBig Pharmaceutical ExampleHosted “Packaged”“Packaged”using cloud “Software as a Service”ERP“Too costly to run this myself, but I’ve made too many customizations”CRMEmail“Home Built”ApplicationHosted “Home Built”“Home Built”using cloud “Platform as a Service”HR SystemMolecule ResearchClinical Trial

20. “Packaged”ApplicationBig Pharmaceutical ExampleHosted “Packaged”“Packaged”using cloud “Software as a Service”ERPCRM“CRM and Email are commodity services – They have no customizations, and it’s cheaper for someone else to run these”Email“Home Built”ApplicationHosted “Home Built”“Home Built”using cloud “Platform as a Service”HR SystemMolecule ResearchClinical Trial

21. Big Pharmaceutical Example“Packaged”ApplicationHosted “Packaged”“Packaged”using cloud “Software as a Service”ERPCRMEmail“Home Built”ApplicationHosted “Home Built”“Home Built”using cloud “Platform as a Service”“I can’t afford to maintain this old HR application written in VB – it’s driving me mad!”HR System“…but due to regulatory issues, I cannot store my HR data off-premise”Molecule ResearchClinical Trial

22. “Packaged”ApplicationBig Pharmaceutical ExampleHosted “Packaged”“Packaged”using cloud “Software as a Service”ERPCRMEmailHR System“Home Built”ApplicationHosted “Home Built”“Home Built”using cloud “Platform as a Service”“I wish I had access to cheaper compute and storage when I need it”Molecule ResearchClinical Trial

23. “Packaged”ApplicationBig Pharmaceutical ExampleHosted “Packaged”“Packaged”using cloud “Software as a Service”ERPCRMEmailHR System“Home Built”ApplicationHosted “Home Built”“Home Built”using cloud “Platform as a Service”Molecule Research“THIS is where I want to spend my IT resources – I’m going to double down on this application!”Clinical Trial

24. Architectural Blueprints

25. Architectural Blueprints

26. Architectural BlueprintsPhysical, DedicatedSingle service on dedicated hardwarePhysical, SharedMultiple services sharing same hardwarePhysical, HPCPhysical hardware supporting HPC scenarioVirtual, SingleSingle instance virtual imageVirtual, SharedMultiple instance virtual image

27. Architectural Blueprints

28. Architectural Blueprints

29. Architectural BlueprintsFileFileshare, flat, page-based RelationalHosted relational database, familiar, transactional, finite UnstructuredKey/value Pair, no atomicity, infinitely scalable

30. Architectural Blueprints

31. Architectural BlueprintsService BusAsynchronous, reliable messaging, publish/subscribe model Peer to PeerNode registration, directory, presence awareness

32. Architectural Blueprints

33. Architectural BlueprintsAuthenticationUsername / Password or claims basedRole Based AuthorizationRole-checking and authorization

34. Architectural Blueprints

35. Architectural BlueprintsEvent BasedTriggered based on events (e.g. document upload) High ThroughputLow latency, high volume (e.g. trading confirmations)

36. Architectural Blueprints

37. Architectural Blueprints

38. Architectural BlueprintsSearchText Search, Image Search, Indexing Content ManagementIndexing, Retrieval, Conflict Management SocialSocial Graphs, Profiles

39. Architectural Blueprints

40. Architectural BlueprintsTransactionPay for each transaction SubscriptionPay per month/period LicensingPay per user/machine AdvertisingAdvert funded model

41. Architectural Blueprints

42. Architectural BlueprintsService CompositionComposition, brokering results, aggregation Line of Business IntegrationService wrapping of mainframe and other LOB applications

43. Architectural Blueprints

44. Architectural BlueprintsBusiness Logic (Rules)Entities (Schema)Workflow (Process)

45. Architectural Blueprints

46. Architectural BlueprintsStaticStatic content, HTML etc DynamicAsynchronous interaction, AJAX etc. RIARich Internet Applications, high visuals, limited offline support StreamingOptimized for content delivery, videos etc.

47. Architectural Blueprints

48. Architectural BlueprintsRSSSyndication services for subscriptions RESTCRUD access to services via HTML Web ServicesSOAP based, WS-I compliant, WS-*

49. Architectural BlueprintsVoiceXMLMobile Application Speech APISIPSession Initiation Protocol – IM ClientsSMTPEmail inbound and outbound deliverySMSMobile inbound and outbound text messaging

50. Architectural Blueprints

51. Architectural Blueprints

52. Architectural BlueprintsBrowserConsumer of web based content, HTML etc., including RIA plug in OfficeOffice Suite, including Email and RSS reader capabilityClient ApplicationRich (Smart) client applications installed locally on machineGadgetsLocally installed, desktop basedInstant MessagingLocally installed Instant Messaging client

53. Architectural Blueprints

54. Architectural BlueprintsSpeechSpeech enabled interfaceSMS / IMText messaging and IM using Mobile DeviceBrowserConsumer of web based content, HTML etc., including RIA plug in OfficeOffice Suite, including Email and RSS reader capabilityClient ApplicationRich (Smart) client applications installed locally on machine

55. Architectural Blueprints

56. Architectural BlueprintsDevicesDedicated devicesConsolesGames Consoles

57. Architectural Blueprints

58. Architectural Trends

59. Architectural TrendsHow can we analyze our architectures using these layers and components?

60. Static Web Site, On Premise

61. Static Web Site, On Premise (Add Content Mgt)

62. Static Web Site, On Premise (Add Search/Social)

63. Static Web Site, On Premise (Add Ad Service)

64. Static Web Site, On Premise (Move to Hoster)

65. Static Web Site, On Premise (Add AJAX)

66. Static Web Site, On Premise (Add Mobile RSS)

67. Architectural TrendsHow about the trends we talked about earlier?

68. Architectural TrendsTrend 1: Service Oriented Architecture (SOA)

69. Trend 1: SOA - Single Service, On Premise

70. Trend 1: SOA - Single Service, On Premise

71. Trend 1: SOA - Single Service, On Premise

72. Trend 1: SOA - Single Service, On Premise

73. Trend 1: SOA - Single Service, On Premise

74. Trend 1: SOA - Single Service, On Premise

75. Trend 1: SOA - Single Service, On Premise

76. Trend 1: SOA - Single Service, On Premise

77. Architectural TrendsTrend 2: Software as a Service (SaaS)

78. Trend 2: SaaS – Web Based SaaS Provider

79. Trend 2: SaaS – Web Based SaaS Provider

80. Trend 2: SaaS – Web Based SaaS Provider

81. Architectural TrendsTrend 3: Web 2.0

82. Trend 3: Web 2.0 – Social Networking Site

83. Trend 3: Web 2.0 – Social Networking Site

84. Architectural TrendsTrend 4: Rich Internet Applications

85. Trend 4: RIA – eCommerce Site

86. Trend 4: RIA – eCommerce Site

87. Trend 4: RIA – eCommerce Site

88. Trend 4: RIA – eCommerce Site

89. Architectural TrendsTrend 5: Cloud Computing

90. Trend 5: Cloud Computing – Backup Provider

91. Trend 5: Cloud Computing – Backup Provider

92. Trend 5: Cloud Computing – Backup Provider

93. Architectural TrendsHow about Microsoft’s own products?

94. Windows Live Mesh CTP (Current, Primary)

95. Exchange Lifecycle (Exchange 4.0, Outlook 97)RPCJET Database

96. Exchange Lifecycle (Exchange 5.0, Outlook 97)RPCActive DirectoryJET Database

97. Exchange Lifecycle (Exchange 5.0 SP1, Outlook XP)OWARPCActive DirectoryJET Database

98. Exchange Lifecycle (Exchange 2003, Outlook 2003)OWARPC over HTTPSActive DirectoryJET Database

99. Exchange Lifecycle (Exchange 2007, Outlook 2007)OWAActive DirectoryJET Database

100. Exchange Lifecycle (Hosted Exchange, Outlook 2007)OWAActive DirectoryJET Database

101. Architectural Challenges

102. “Packaged”ApplicationBig Pharmaceutical ExampleHosted “Packaged”“Packaged”using cloud “Software as a Service”ERPCRMEmailHR System“Home Built”ApplicationHosted “Home Built”“Home Built”using cloud “Platform as a Service”Molecule ResearchClinical Trial

103. Architectural ChallengesChallenge 1 - Identity

104. Challenge 1 - Identity

105. Challenge 1 - Identity

106. Challenge 1 - Identity Accessing Hosted Assets with Internal Credentials

107. AuthN and AuthZ across FW

108. Credential StorageChallenge 1 - Identity Issuing Authority

109. Relying Party

110. Authentication AssuranceSTS-ISTS-R

111. “A Cloudy World” ExampleClinical trial patientsemployeesITSTS(big pharma instance in purple)Hosted ERP @ HosterDirectoryThe “Cloud”(big pharma data in purple)ManagementCRM OnlineBig Pharma “on premise”FirewallCloud StorageSTSRelay Cloud Compute Clinical trialsoftwareInternetService Bus(Connectivity)InternetService Bus(Identity) (new molecule research in purple)Cloud Platform

112. Architectural ChallengesChallenge 2 – Data

113. Challenge 2 - Data

114. Challenge 2 - Data Import and Export of Data

115. Privacy of External Data

116. Reporting and Analytics

117. Database of RecordArchitectural ChallengesChallenge 3 – Management

118. Challenge 3 - Management

119. Challenge 3 - Management Holistic View of Application?

120. Integration into existing System Management solutions?

121. Contracts and SLAsArchitectural Blueprints – Next Steps

122. Architectural Blueprints – Next StepsStep 1 – Use the “blueprints” to decompose and recompose existing applications

123. Architectural Blueprints – Next StepsStep 2 – Get the right people involved