Your SlideShare is downloading. ×
 
Heads in the Cloud, Feet on the Ground Philip Meyer Technology Specialist – Hosting Microsoft Pty Ltd philme@microsoft.com
Heads in the Cloud, Feet on the Ground When it comes to running applications, organizations today face a tension between c...
Heads in the Cloud, Feet on the Ground Economy of Scale Low High Control High Low Application runs  on-premise Buy my own ...
Heads in the Cloud, Feet on the Ground Tension between build vs. buy Build vs. Buy Build Buy
Heads in the Cloud, Feet on the Ground “ Packaged” Application An application that I buy “off the shelf” and run myself “ ...
Big Pharmaceutical Example “ Too costly to run this myself, but I’ve made too many customizations” “ Packaged” Application...
Big Pharmaceutical Example “ CRM and Email are commodity services – They have no customizations, and it’s cheaper for some...
Big Pharmaceutical Example “ I can’t afford to maintain this old HR application written in VB – it’s driving me mad!” “… b...
Big Pharmaceutical Example “ I wish I had access to cheaper compute and storage when I need it” “ Packaged” Application “ ...
Big Pharmaceutical Example “ THIS is where I want to spend my IT resources – I’m going to double down on this application!...
Architectural Principles for Software + Services
Architectural Principles for Software + Services
Architectural Principles for Software + Services Physical, Dedicated Single service on dedicated hardware Physical, Shared...
Architectural Principles for Software + Services
Architectural Principles for Software + Services
Architectural Principles for Software + Services File Fileshare, flat, page-based  Relational Hosted relational database, ...
Architectural Principles for Software + Services
Architectural Principles for Software + Services Service Bus Asynchronous, reliable messaging, publish/subscribe model  Pe...
Architectural Principles for Software + Services
Architectural Principles for Software + Services Authentication Username / Password or claims based Role Based Authorizati...
Architectural Principles for Software + Services
Architectural Principles for Software + Services Event Based Triggered based on events (e.g. document upload)  High Throug...
Architectural Principles for Software + Services
Architectural Principles for Software + Services
Architectural Principles for Software + Services Search Text Search, Image Search, Indexing  Social Social Graphs, Profile...
Architectural Principles for Software + Services
Architectural Principles for Software + Services Transaction Pay for each transaction  Subscription Pay per month/period  ...
Architectural Principles for Software + Services
Architectural Principles for Software + Services Service Composition Composition, brokering results, aggregation  Line of ...
Architectural Principles for Software + Services
Architectural Principles for Software + Services Business Logic  (Rules) Entities  (Schema) Workflow  (Process)
Architectural Principles for Software + Services
Architectural Principles for Software + Services Static Static content, HTML etc  Dynamic Asynchronous interaction, AJAX e...
Architectural Principles for Software + Services
Architectural Principles for Software + Services Web Services SOAP based, WS-I compliant, WS-*  REST CRUD access to servic...
Architectural Principles for Software + Services VoiceXML Mobile Application Speech API SIP Session Initiation Protocol – ...
Architectural Principles for Software + Services
Architectural Principles for Software + Services
Architectural Principles for Software + Services Browser Consumer of web based content, HTML etc., including RIA plug in  ...
Architectural Principles for Software + Services
Architectural Principles for Software + Services Browser Consumer of web based content, HTML etc., including RIA plug in  ...
Architectural Principles for Software + Services
Architectural Principles for Software + Services Devices Dedicated devices Consoles Games Consoles
Architectural Principles for Software + Services
Architectural Principles for Software + Services
Architectural Principles for Software + Services What type of architectural patterns can we show using these principles?
Static Web Site, On Premise
Static Web Site, On Premise (Add Content Mgt)
Static Web Site, On Premise (Add Search/Social)
Static Web Site, On Premise (Add Ad Service)
Static Web Site, On Premise (Move to Hoster)
Static Web Site, On Premise (Add AJAX)
Static Web Site, On Premise (Add Mobile RSS)
Architectural Principles for Software + Services How about the trends we talked about earlier?
Architectural Principles for Software + Services Trend 1: Service Oriented Architecture (SOA)
Trend 1: SOA - Single Service, On Premise
Trend 1: SOA - Single Service, On Premise
Trend 1: SOA - Single Service, On Premise
Trend 1: SOA - Single Service, On Premise
Trend 1: SOA - Single Service, On Premise
Trend 1: SOA - Single Service, On Premise
Trend 1: SOA - Single Service, On Premise
Trend 1: SOA - Single Service, On Premise
 
Architectural Principles for Software + Services Trend 2: Software as a Service (SaaS)
Trend 2: SaaS – Web Based SaaS Provider
Trend 2: SaaS – Web Based SaaS Provider
Trend 2: SaaS – Web Based SaaS Provider
Architectural Principles for Software + Services Trend 3: Web 2.0
Trend 3: Web 2.0 – Social Networking Site
Trend 3: Web 2.0 – Social Networking Site
 
Architectural Principles for Software + Services Trend 4: Rich Internet Applications
Trend 4: RIA – eCommerce Site
Trend 4: RIA – eCommerce Site
Trend 4: RIA – eCommerce Site
Trend 4: RIA – eCommerce Site
 
Architectural Principles for Software + Services Trend 5: Cloud Computing
Trend 5: Cloud Computing – Backup Provider
Trend 5: Cloud Computing – Backup Provider
Trend 5: Cloud Computing – Backup Provider
Architectural Principles for Software + Services How about Microsoft’s own products?
Windows Live Mesh CTP (Current, Primary)
Exchange Lifecycle (Exchange 4.0, Outlook 97)
Exchange Lifecycle (Exchange 5.0, Outlook 97)
Exchange Lifecycle (Exchange 5.0 SP1, Outlook XP)
Exchange Lifecycle (Exchange 2003, Outlook 2003)
Exchange Lifecycle (Exchange 2007, Outlook 2007)
Exchange Lifecycle (Hosted Exchange, Outlook 2007)
Architectural Challenges
Big Pharmaceutical Example “ Packaged” Application “ Home Built” Application Hosted  “ Home Built” Hosted  “ Packaged” “ H...
Architectural Challenges Challenge 1 - Identity
Challenge 1 - Identity
Challenge 1 - Identity
Challenge 1 - Identity <ul><li>Accessing Hosted Assets with Internal Credentials </li></ul><ul><li>AuthN and AuthZ across ...
Challenge 1 - Identity
Architectural Challenges Challenge 2 – Data
Challenge 2 - Data
Challenge 2 - Data <ul><li>Import and Export of Data </li></ul><ul><li>Privacy of External Data </li></ul><ul><li>Reportin...
Architectural Challenges Challenge 3 – Management
Challenge 3 - Management
Challenge 3 - Management <ul><li>Holistic View of Application? </li></ul><ul><li>Integration into existing System Manageme...
Software + Services – Next Steps
Software + Services – Next Steps Step 1 – Use the “principles” to decompose and recompose existing applications
Software + Services – Next Steps Step 2 – Get the right people involved
Software + Services – Next Steps Infrastructure Architect / Data Center Operations Solutions and Infrastructure Architect ...
Software + Services – Next Steps Step 3 – Understand the Technology Mappings
Software + Services – Next Steps IE8 Windows Mobile 7 XBOX 360 IIS 7 SL Streaming WCF .NET Framework MOSS 2007 BTS Adapter...
Software + Services – Next Steps Step 4 – Blueprints for repeatable patterns
Software + Services – Next Steps
Software + Services – Next Steps
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be...
Upcoming SlideShare
Loading in...5
×

Innovation Days 2008: Architecture Principles For S+S

4,470

Published on

2 of 6: Phil Meyer & Andrew Coates presents Architecture Principles for Software plus Services

Published in: Technology, Business
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
4,470
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Transcript of "Innovation Days 2008: Architecture Principles For S+S"

  1. 2. Heads in the Cloud, Feet on the Ground Philip Meyer Technology Specialist – Hosting Microsoft Pty Ltd philme@microsoft.com
  2. 3. Heads in the Cloud, Feet on the Ground When it comes to running applications, organizations today face a tension between control and economy of scale Economy of Scale Low High Control High Low
  3. 4. Heads in the Cloud, Feet on the Ground Economy of Scale Low High Control High Low Application runs on-premise Buy my own hardware, and manage my own data center Application runs at a hoster Pay someone to host my application using hardware that I specify Application runs using cloud platform Pay someone to host my application without specifying the hardware (they promise to be “infinitely” scalable) Application is supplied by a vendor Pay for someone’s hosted application. Don’t care about the hardware, as long as it works.
  4. 5. Heads in the Cloud, Feet on the Ground Tension between build vs. buy Build vs. Buy Build Buy
  5. 6. Heads in the Cloud, Feet on the Ground “ Packaged” Application An application that I buy “off the shelf” and run myself “ Home Built” Application An application that I develop and run myself Build vs. Buy Build Buy Hosted “ Home Built” An application that I develop myself, but run at a hoster Hosted “ Packaged” An application that I buy “off the shelf” and then run at a hoster “ Home Built” using cloud An application that I develop myself, that is hosted using cloud platform “ 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 vendor “ Platform as a Service” A vendor hosted development and runtime environment
  6. 7. Big Pharmaceutical Example “ Too costly to run this myself, but I’ve made too many customizations” “ Packaged” Application “ Home Built” Application Hosted “ Home Built” Hosted “ Packaged” “ Home Built” using cloud “ Packaged” using cloud “ Software as a Service” “ Platform as a Service” Clinical Trial Molecule Research HR System Email CRM ERP
  7. 8. Big Pharmaceutical Example “ CRM and Email are commodity services – They have no customizations, and it’s cheaper for someone else to run these” “ Packaged” Application “ Home Built” Application Hosted “ Home Built” Hosted “ Packaged” “ Home Built” using cloud “ Packaged” using cloud “ Software as a Service” “ Platform as a Service” Clinical Trial Molecule Research HR System Email CRM ERP
  8. 9. Big Pharmaceutical Example “ I can’t afford to maintain this old HR application written in VB – it’s driving me mad!” “… but due to regulatory issues, I cannot store my HR data off-premise” “ Packaged” Application “ Home Built” Application Hosted “ Home Built” Hosted “ Packaged” “ Home Built” using cloud “ Packaged” using cloud “ Software as a Service” “ Platform as a Service” Clinical Trial Molecule Research HR System Email CRM ERP
  9. 10. Big Pharmaceutical Example “ I wish I had access to cheaper compute and storage when I need it” “ Packaged” Application “ Home Built” Application Hosted “ Home Built” Hosted “ Packaged” “ Home Built” using cloud “ Packaged” using cloud “ Software as a Service” “ Platform as a Service” Clinical Trial Molecule Research Email CRM ERP HR System
  10. 11. Big Pharmaceutical Example “ THIS is where I want to spend my IT resources – I’m going to double down on this application!” “ Packaged” Application “ Home Built” Application Hosted “ Home Built” Hosted “ Packaged” “ Home Built” using cloud “ Packaged” using cloud “ Software as a Service” “ Platform as a Service” Clinical Trial Molecule Research Email CRM ERP HR System
  11. 12. Architectural Principles for Software + Services
  12. 13. Architectural Principles for Software + Services
  13. 14. Architectural Principles for Software + Services Physical, Dedicated Single service on dedicated hardware Physical, Shared Multiple services sharing same hardware Physical, HPC Physical hardware supporting HPC scenario Virtual, Single Single instance virtual image Virtual, Shared Multiple instance virtual image
  14. 15. Architectural Principles for Software + Services
  15. 16. Architectural Principles for Software + Services
  16. 17. Architectural Principles for Software + Services File Fileshare, flat, page-based Relational Hosted relational database, familiar, transactional, finite Unstructured Key/value Pair, no atomicity, infinitely scalable
  17. 18. Architectural Principles for Software + Services
  18. 19. Architectural Principles for Software + Services Service Bus Asynchronous, reliable messaging, publish/subscribe model Peer to Peer Node registration, directory, presence awareness
  19. 20. Architectural Principles for Software + Services
  20. 21. Architectural Principles for Software + Services Authentication Username / Password or claims based Role Based Authorization Role-checking and authorization
  21. 22. Architectural Principles for Software + Services
  22. 23. Architectural Principles for Software + Services Event Based Triggered based on events (e.g. document upload) High Throughput Low latency, high volume (e.g. trading confirmations)
  23. 24. Architectural Principles for Software + Services
  24. 25. Architectural Principles for Software + Services
  25. 26. Architectural Principles for Software + Services Search Text Search, Image Search, Indexing Social Social Graphs, Profiles Content Management Indexing, Retrieval, Conflict Management
  26. 27. Architectural Principles for Software + Services
  27. 28. Architectural Principles for Software + Services Transaction Pay for each transaction Subscription Pay per month/period Licensing Pay per user/machine Advertising Advert funded model
  28. 29. Architectural Principles for Software + Services
  29. 30. Architectural Principles for Software + Services Service Composition Composition, brokering results, aggregation Line of Business Integration Service wrapping of mainframe and other LOB applications
  30. 31. Architectural Principles for Software + Services
  31. 32. Architectural Principles for Software + Services Business Logic (Rules) Entities (Schema) Workflow (Process)
  32. 33. Architectural Principles for Software + Services
  33. 34. Architectural Principles for Software + Services Static Static content, HTML etc Dynamic Asynchronous interaction, AJAX etc. RIA Rich Internet Applications, high visuals, limited offline support Streaming Optimized for content delivery, videos etc.
  34. 35. Architectural Principles for Software + Services
  35. 36. Architectural Principles for Software + Services Web Services SOAP based, WS-I compliant, WS-* REST CRUD access to services via HTML RSS Syndication services for subscriptions
  36. 37. Architectural Principles for Software + Services VoiceXML Mobile Application Speech API SIP Session Initiation Protocol – IM Clients SMTP Email inbound and outbound delivery SMS Mobile inbound and outbound text messaging
  37. 38. Architectural Principles for Software + Services
  38. 39. Architectural Principles for Software + Services
  39. 40. Architectural Principles for Software + Services Browser Consumer of web based content, HTML etc., including RIA plug in Office Office Suite, including Email and RSS reader capability Client Application Rich (Smart) client applications installed locally on machine Gadgets Locally installed, desktop based Instant Messaging Locally installed Instant Messaging client
  40. 41. Architectural Principles for Software + Services
  41. 42. Architectural Principles for Software + Services Browser Consumer of web based content, HTML etc., including RIA plug in Office Office Suite, including Email and RSS reader capability Client Application Rich (Smart) client applications installed locally on machine SMS / IM Text messaging and IM using Mobile Device Speech Speech enabled interface
  42. 43. Architectural Principles for Software + Services
  43. 44. Architectural Principles for Software + Services Devices Dedicated devices Consoles Games Consoles
  44. 45. Architectural Principles for Software + Services
  45. 46. Architectural Principles for Software + Services
  46. 47. Architectural Principles for Software + Services What type of architectural patterns can we show using these principles?
  47. 48. Static Web Site, On Premise
  48. 49. Static Web Site, On Premise (Add Content Mgt)
  49. 50. Static Web Site, On Premise (Add Search/Social)
  50. 51. Static Web Site, On Premise (Add Ad Service)
  51. 52. Static Web Site, On Premise (Move to Hoster)
  52. 53. Static Web Site, On Premise (Add AJAX)
  53. 54. Static Web Site, On Premise (Add Mobile RSS)
  54. 55. Architectural Principles for Software + Services How about the trends we talked about earlier?
  55. 56. Architectural Principles for Software + Services Trend 1: Service Oriented Architecture (SOA)
  56. 57. Trend 1: SOA - Single Service, On Premise
  57. 58. Trend 1: SOA - Single Service, On Premise
  58. 59. Trend 1: SOA - Single Service, On Premise
  59. 60. Trend 1: SOA - Single Service, On Premise
  60. 61. Trend 1: SOA - Single Service, On Premise
  61. 62. Trend 1: SOA - Single Service, On Premise
  62. 63. Trend 1: SOA - Single Service, On Premise
  63. 64. Trend 1: SOA - Single Service, On Premise
  64. 66. Architectural Principles for Software + Services Trend 2: Software as a Service (SaaS)
  65. 67. Trend 2: SaaS – Web Based SaaS Provider
  66. 68. Trend 2: SaaS – Web Based SaaS Provider
  67. 69. Trend 2: SaaS – Web Based SaaS Provider
  68. 70. Architectural Principles for Software + Services Trend 3: Web 2.0
  69. 71. Trend 3: Web 2.0 – Social Networking Site
  70. 72. Trend 3: Web 2.0 – Social Networking Site
  71. 74. Architectural Principles for Software + Services Trend 4: Rich Internet Applications
  72. 75. Trend 4: RIA – eCommerce Site
  73. 76. Trend 4: RIA – eCommerce Site
  74. 77. Trend 4: RIA – eCommerce Site
  75. 78. Trend 4: RIA – eCommerce Site
  76. 80. Architectural Principles for Software + Services Trend 5: Cloud Computing
  77. 81. Trend 5: Cloud Computing – Backup Provider
  78. 82. Trend 5: Cloud Computing – Backup Provider
  79. 83. Trend 5: Cloud Computing – Backup Provider
  80. 84. Architectural Principles for Software + Services How about Microsoft’s own products?
  81. 85. Windows Live Mesh CTP (Current, Primary)
  82. 86. Exchange Lifecycle (Exchange 4.0, Outlook 97)
  83. 87. Exchange Lifecycle (Exchange 5.0, Outlook 97)
  84. 88. Exchange Lifecycle (Exchange 5.0 SP1, Outlook XP)
  85. 89. Exchange Lifecycle (Exchange 2003, Outlook 2003)
  86. 90. Exchange Lifecycle (Exchange 2007, Outlook 2007)
  87. 91. Exchange Lifecycle (Hosted Exchange, Outlook 2007)
  88. 92. Architectural Challenges
  89. 93. Big Pharmaceutical Example “ Packaged” Application “ Home Built” Application Hosted “ Home Built” Hosted “ Packaged” “ Home Built” using cloud “ Packaged” using cloud “ Software as a Service” “ Platform as a Service” Clinical Trial Molecule Research Email CRM ERP HR System
  90. 94. Architectural Challenges Challenge 1 - Identity
  91. 95. Challenge 1 - Identity
  92. 96. Challenge 1 - Identity
  93. 97. Challenge 1 - Identity <ul><li>Accessing Hosted Assets with Internal Credentials </li></ul><ul><li>AuthN and AuthZ across FW </li></ul><ul><li>Credential Storage </li></ul>
  94. 98. Challenge 1 - Identity
  95. 99. Architectural Challenges Challenge 2 – Data
  96. 100. Challenge 2 - Data
  97. 101. Challenge 2 - Data <ul><li>Import and Export of Data </li></ul><ul><li>Privacy of External Data </li></ul><ul><li>Reporting and Analytics </li></ul>
  98. 102. Architectural Challenges Challenge 3 – Management
  99. 103. Challenge 3 - Management
  100. 104. Challenge 3 - Management <ul><li>Holistic View of Application? </li></ul><ul><li>Integration into existing System Management solutions? </li></ul><ul><li>Contracts and SLAs </li></ul>
  101. 105. Software + Services – Next Steps
  102. 106. Software + Services – Next Steps Step 1 – Use the “principles” to decompose and recompose existing applications
  103. 107. Software + Services – Next Steps Step 2 – Get the right people involved
  104. 108. Software + Services – Next Steps Infrastructure Architect / Data Center Operations Solutions and Infrastructure Architect Solutions Architect and Development Team Solutions Architect and Development Team (inc. Web Design) Solutions Architect and Development Team (inc. Designer) Enterprise Architect and CIO Data Center Operations
  105. 109. Software + Services – Next Steps Step 3 – Understand the Technology Mappings
  106. 110. Software + Services – Next Steps IE8 Windows Mobile 7 XBOX 360 IIS 7 SL Streaming WCF .NET Framework MOSS 2007 BTS Adapters MOSS 2007 BDC AD / ADFS Ad Center .NET Framework 3 rd Party BizTalk 2006 R2 ILM BizTalk / BizTalk.Net Mesh CTP IIS 7 SQL Server SSDS Windows WF MOSS 2007 Windows WF BizTalk Server Windows Server 2008 WS 2008 HPC Windows Server 2008 Hyper-V Office WPF Vista OC Win Embed .NET CF
  107. 111. Software + Services – Next Steps Step 4 – Blueprints for repeatable patterns
  108. 112. Software + Services – Next Steps
  109. 113. Software + Services – Next Steps
  110. 114. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

×