16. 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
17. Heads in the Cloud, Feet on the Ground Economy of Scale Low High Control High Low Application runs on-premises 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)
18. Heads in the Cloud, Feet on the Ground On Premises vs. Cloud On Premises Cloud Application runs on-premises 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)
19. Heads in the Cloud, Feet on the Ground On Premises vs. Cloud On Premises Cloud Application runs on-premises 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) Build vs. Buy Build Buy
20. Heads in the Cloud, Feet on the Ground On Premises vs. Cloud On Premises Cloud “ Packaged” Application An application that I buy “off the shelf” and run myself “ Home Built” Application An application that I develop and run myself 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 Cloud Platform An application that I develop myself, that I run in the cloud “ Software as a Service” A hosted application that I buy from a vendor Build vs. Buy Build Buy
21. Heads in the Cloud, Feet on the Ground On Premises vs. Cloud On Premises Cloud Build vs. Buy Build Buy “ Packaged” Application “ Home Built” Application Hosted “ Home Built” Hosted “ Packaged” Cloud Platform “ Software as a Service”
22. Heads in the Cloud, Feet on the Ground On Premises vs. Cloud On Premises Cloud “ Too costly to run this myself, but I’ve made too many customizations” “ Packaged” Application “ Home Built” Application Hosted “ Home Built” Hosted “ Packaged” Cloud Platform “ Software as a Service” Build vs. Buy Build Buy Clinical Trial Molecule Research HR System Email CRM ERP
23. Heads in the Cloud, Feet on the Ground On Premises vs. Cloud On Premises Cloud “ 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” Cloud Platform “ Software as a Service” Build vs. Buy Build Buy Clinical Trial Molecule Research HR System Email CRM ERP
24. Heads in the Cloud, Feet on the Ground On Premises vs. Cloud On Premises Cloud “ 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” Cloud Platform “ Software as a Service” Build vs. Buy Build Buy Clinical Trial Molecule Research HR System Email CRM ERP
25. Heads in the Cloud, Feet on the Ground On Premises vs. Cloud On Premises Cloud “ I wish I had access to cheaper compute and storage when I need it” “ Packaged” Application “ Home Built” Application Hosted “ Home Built” Hosted “ Packaged” Cloud Platform “ Software as a Service” Build vs. Buy Build Buy Clinical Trial Molecule Research Email CRM ERP HR System
26. Heads in the Cloud, Feet on the Ground On Premises vs. Cloud On Premises Cloud “ 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” Cloud Platform “ Software as a Service” Build vs. Buy Build Buy Clinical Trial Molecule Research Email CRM ERP HR System
34. Architectural Principles for Software + Services Service Bus Asynchronous, reliable messaging, publish/subscribe model Peer to Peer Node registration, directory, presence awareness
36. Architectural Principles for Software + Services Authentication Username / Password or claims based Role Based Authorization Role-checking and authorization
38. 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)
43. Architectural Principles for Software + Services Transaction Pay for each transaction Subscription Pay per month/period Licensing Pay per user/machine Advertising Advert funded model
45. Architectural Principles for Software + Services Service Composition Composition, brokering results, aggregation Line of Business Integration Service wrapping of mainframe and other LOB applications
49. 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.
51. 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
52. 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
55. 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
57. 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
117. Software + Services – Next Steps Step 1 – Understand many successful applications are a combination of Software + Services
118. Software + Services – Next Steps Step 2 – Use the “principles” to visualize, decompose and recompose existing applications
119. Software + Services – Next Steps Step 3 – Understand the Technology Mappings
120. 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 .NET Services Ad Center .NET Framework 3 rd Party BizTalk 2006 R2 ILM .NET Services BizTalk / BizTalk.Net Live Services IIS 7 SQL Server SQL Services Windows WF MOSS 2007 .NET Services Windows WF BizTalk Server .NET Services Windows Server 2008 WS 2008 HPC Windows Server 2008 Hyper-V Office WPF Vista OC Win Embed .NET CF Windows Azure
121. Software + Services – Next Steps Step 4 – Blueprints for repeatable patterns
125. 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