• Save
Innovation Days 2008: Architecture Principles For S+S
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Innovation Days 2008: Architecture Principles For S+S

  • 2,164 views
Uploaded on

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

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

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,164
On Slideshare
2,087
From Embeds
77
Number of Embeds
3

Actions

Shares
Downloads
0
Comments
0
Likes
4

Embeds 77

http://zankke.tistory.com 73
http://www.slideshare.net 3
http://blogs.msdn.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1.  
  • 2. Heads in the Cloud, Feet on the Ground Philip Meyer Technology Specialist – Hosting Microsoft Pty Ltd philme@microsoft.com
  • 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
  • 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.
  • 5. Heads in the Cloud, Feet on the Ground Tension between build vs. buy Build vs. Buy Build Buy
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 12. Architectural Principles for Software + Services
  • 13. Architectural Principles for Software + Services
  • 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
  • 15. Architectural Principles for Software + Services
  • 16. Architectural Principles for Software + Services
  • 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
  • 18. Architectural Principles for Software + Services
  • 19. Architectural Principles for Software + Services Service Bus Asynchronous, reliable messaging, publish/subscribe model Peer to Peer Node registration, directory, presence awareness
  • 20. Architectural Principles for Software + Services
  • 21. Architectural Principles for Software + Services Authentication Username / Password or claims based Role Based Authorization Role-checking and authorization
  • 22. Architectural Principles for Software + Services
  • 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)
  • 24. Architectural Principles for Software + Services
  • 25. Architectural Principles for Software + Services
  • 26. Architectural Principles for Software + Services Search Text Search, Image Search, Indexing Social Social Graphs, Profiles Content Management Indexing, Retrieval, Conflict Management
  • 27. Architectural Principles for Software + Services
  • 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
  • 29. Architectural Principles for Software + Services
  • 30. Architectural Principles for Software + Services Service Composition Composition, brokering results, aggregation Line of Business Integration Service wrapping of mainframe and other LOB applications
  • 31. Architectural Principles for Software + Services
  • 32. Architectural Principles for Software + Services Business Logic (Rules) Entities (Schema) Workflow (Process)
  • 33. Architectural Principles for Software + Services
  • 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.
  • 35. Architectural Principles for Software + Services
  • 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
  • 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
  • 38. Architectural Principles for Software + Services
  • 39. Architectural Principles for Software + Services
  • 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
  • 41. Architectural Principles for Software + Services
  • 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
  • 43. Architectural Principles for Software + Services
  • 44. Architectural Principles for Software + Services Devices Dedicated devices Consoles Games Consoles
  • 45. Architectural Principles for Software + Services
  • 46. Architectural Principles for Software + Services
  • 47. Architectural Principles for Software + Services What type of architectural patterns can we show using these principles?
  • 48. Static Web Site, On Premise
  • 49. Static Web Site, On Premise (Add Content Mgt)
  • 50. Static Web Site, On Premise (Add Search/Social)
  • 51. Static Web Site, On Premise (Add Ad Service)
  • 52. Static Web Site, On Premise (Move to Hoster)
  • 53. Static Web Site, On Premise (Add AJAX)
  • 54. Static Web Site, On Premise (Add Mobile RSS)
  • 55. Architectural Principles for Software + Services How about the trends we talked about earlier?
  • 56. Architectural Principles for Software + Services Trend 1: Service Oriented Architecture (SOA)
  • 57. Trend 1: SOA - Single Service, On Premise
  • 58. Trend 1: SOA - Single Service, On Premise
  • 59. Trend 1: SOA - Single Service, On Premise
  • 60. Trend 1: SOA - Single Service, On Premise
  • 61. Trend 1: SOA - Single Service, On Premise
  • 62. Trend 1: SOA - Single Service, On Premise
  • 63. Trend 1: SOA - Single Service, On Premise
  • 64. Trend 1: SOA - Single Service, On Premise
  • 65.  
  • 66. Architectural Principles for Software + Services Trend 2: Software as a Service (SaaS)
  • 67. Trend 2: SaaS – Web Based SaaS Provider
  • 68. Trend 2: SaaS – Web Based SaaS Provider
  • 69. Trend 2: SaaS – Web Based SaaS Provider
  • 70. Architectural Principles for Software + Services Trend 3: Web 2.0
  • 71. Trend 3: Web 2.0 – Social Networking Site
  • 72. Trend 3: Web 2.0 – Social Networking Site
  • 73.  
  • 74. Architectural Principles for Software + Services Trend 4: Rich Internet Applications
  • 75. Trend 4: RIA – eCommerce Site
  • 76. Trend 4: RIA – eCommerce Site
  • 77. Trend 4: RIA – eCommerce Site
  • 78. Trend 4: RIA – eCommerce Site
  • 79.  
  • 80. Architectural Principles for Software + Services Trend 5: Cloud Computing
  • 81. Trend 5: Cloud Computing – Backup Provider
  • 82. Trend 5: Cloud Computing – Backup Provider
  • 83. Trend 5: Cloud Computing – Backup Provider
  • 84. Architectural Principles for Software + Services How about Microsoft’s own products?
  • 85. Windows Live Mesh CTP (Current, Primary)
  • 86. Exchange Lifecycle (Exchange 4.0, Outlook 97)
  • 87. Exchange Lifecycle (Exchange 5.0, Outlook 97)
  • 88. Exchange Lifecycle (Exchange 5.0 SP1, Outlook XP)
  • 89. Exchange Lifecycle (Exchange 2003, Outlook 2003)
  • 90. Exchange Lifecycle (Exchange 2007, Outlook 2007)
  • 91. Exchange Lifecycle (Hosted Exchange, Outlook 2007)
  • 92. Architectural Challenges
  • 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
  • 94. Architectural Challenges Challenge 1 - Identity
  • 95. Challenge 1 - Identity
  • 96. Challenge 1 - Identity
  • 97. Challenge 1 - Identity
    • Accessing Hosted Assets with Internal Credentials
    • AuthN and AuthZ across FW
    • Credential Storage
  • 98. Challenge 1 - Identity
  • 99. Architectural Challenges Challenge 2 – Data
  • 100. Challenge 2 - Data
  • 101. Challenge 2 - Data
    • Import and Export of Data
    • Privacy of External Data
    • Reporting and Analytics
  • 102. Architectural Challenges Challenge 3 – Management
  • 103. Challenge 3 - Management
  • 104. Challenge 3 - Management
    • Holistic View of Application?
    • Integration into existing System Management solutions?
    • Contracts and SLAs
  • 105. Software + Services – Next Steps
  • 106. Software + Services – Next Steps Step 1 – Use the “principles” to decompose and recompose existing applications
  • 107. Software + Services – Next Steps Step 2 – Get the right people involved
  • 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
  • 109. Software + Services – Next Steps Step 3 – Understand the Technology Mappings
  • 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
  • 111. Software + Services – Next Steps Step 4 – Blueprints for repeatable patterns
  • 112. Software + Services – Next Steps
  • 113. Software + Services – Next Steps
  • 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.