Mobile & Cloud Computing Merge to Form a Supernova of Computing Opportunities. Gregory S. Smith Chief Technology Officer ASCD & Author

Transcription

1 Mobile & Cloud Computing Merge to Form a Supernova of Computing Opportunities Gregory S. Smith Chief Technology Officer ASCD & Author

2 Agenda 1. Brief History of IT Architectures Are We Learning from Our Past? 2. Cloud and Mobile Converge 3. Mobile Successes 4. Cloud Successes 5. Re-Thinking the Mobile Delivery Architecture 6. Where Do We Go from Here?

3 Brief History of IT Architectures

4 Web-based, then SaaS Architecture Deploy and Upgrade 1 Version of the Truth for the Code. N- Tier Web was the Stepping Stone for SaaS on Multi-tenant, Elastic Computing with a Subscription Model HTTP / HTTPS Web / / Public / Private Cloud or On-Premise Data Centers Web / Browser-based Delivery via HTML-X Standard Customer Data

5 Mobile and Cloud Converge Registration / Clearinghouse and Download for s - Apple - Google Public Web / / Public / Private Cloud or On-Premise Data Centers Web to Update Data on Client Device When Connected to the Web /

6 Driving Force: Mobile Growth Google Play Hit 1 Million Apps in July Million Downloaded Apple App Store Hit 1 Million in October Million Downloaded What s Leading the Charge Top Charts? Fee 1. Minecraft 2. Loopy HD 3. Surgeon Simulator 4. Sky Guide 31. Angry Birds Free 1. Smash Hit Surgeon Sky Guide 4. Calculator 5. Angry Birds Go! 9. Netflix Top Grossing 1. Candy Crush

7 Mobile Growth Some Interesting Apps Out There Thousands of Calculators, Games, Entertainment, Business Apps 28 Disaster Recovery Apps What About Some of the Top SaaS Vendors Oracle 51 SAP Salesforce.com 96 4 Amazon Web Service 1

8 Mobile Successes Taser International McDonalds McD App

9 Cloud Successes Leading Cloud Vendors (P/IaaS, SaaS)

10 Limitations of Mobile s Architecture Registration / Clearinghouse and Download for s - Apple - Google Step 1: Vendor Registers, Data Interaction via Vendor when Run Environment Public / Private Cloud or On- Premise Data Centers Web to Update Data on Client Device When Connected to the Web / Step 2: Consumer Original Download of the Mobile Step 3: Consumer Uses the Step 5: Consumer Downloads the Upgrade to the Step 4: Vendor Modifies the Mobile via Versioning / Enhancements 1.0, 2.0, etc. and Registers in Clearinghouse Note: If the application is any good, it could be installed and re-updated on millions of devices. If the consumer choses NOT to install the update, the vendor s help desk must deal with multiple application versions on multiple versions of the operating system. Ex: Candy Crush has had 25 versions to date for ios only.

11 Limitations of Mobile s Architecture What is this Architecture Called? Registration / Clearinghouse and Download for s - Apple - Google Public Step 1: Vendor Registers, Data Interaction via Vendor when Run Environment Public / Private Cloud or On-Premise Data Centers Step 2: Consumer Original Download of the Mobile Web to Update Data on Client Device When Connected to the Step 5: Consumer Downloads the Upgrade to the Web / Step 3: Consumer Uses the Step 4: Vendor Modifies the Mobile via Versioning / Enhancements 1.0, 2.0, etc. and Registers in Clearinghouse

12 Limitations of Mobile s Architecture Registration / Clearinghouse and Download for s - Apple - Google Client / Server 2.0! With up to triple the development effort to deploy on Windows, Android and ios Public Environment Public / Private Cloud or On-Premise Data Centers Apple and Google Have Evolved to be the New AOL / Yahoo Marketplace Where People Go / Search for Apps and Content. Web to Update Data on Client Device When Connected to the Web / Do we remember why we left this architecture for a web-based N-tier architecture? ** Because of all the headaches deploying and managing versions to millions of client devices.

13 Limitations of Mobile s Architecture Remember the Simplicity of the Web Architecture and the Evolution of SaaS? Environment Public / Private Cloud or On-Premise Data Centers HTTP / HTTPS Browser-based Delivery via HTML-X Standard Web / Customer Data

14 Where Do We Go From Here Registration / Clearinghouse and Download for s - Apple - Google Mobile Hybrid Virtualization Web Question 2: What is the Marketplace of the Future and Does it Have to be Restrictive? There s Nothing Today to Prevent a Vendor from being the Clearinghouse for their s. Public / Virtualization Environment Public / Private Cloud or On- Premise Data Centers Why Virtualization? We Do This Today with Tools Like Citrix, VMWare, and Microsoft. Question 1: What is the client device virtualization standard? Virtualization Software / Standard Built into HTML-X or Deployed as a Virtualization Engine / Container s Run in a Virtual Session Connected to the Vendor s Server Farm and Presented back to the Device (On-line and Off-line) Web / Customer Data

15 Where Do We Go From Here Mobile Hybrid Virtualization Web Why Not Just do SaaS? Because We Want Off-line and On-line Usage, Security, Provisioning of Apps, Control of Versioning and No Code on the Client Device Registration / Clearinghouse and Download for s - Apple - Google - Vendor Public / Virtualization Environment Public / Private Cloud or On-Premise Data Centers Web / App Virtualization with Off-Line Capability Customer Data

16 If We Could Redesign Mobile Today, Is This What We Would Build? We Can Do Better Public Registration / Clearinghouse and Download for s - Apple - Google Web / Environment Public / Private Cloud or On-Premise Data Centers

17 Hybrid Virtualization Web Public / Virtualization Environment Public / Private Cloud or On- Premise Data Centers Web / App Virtualization with Off-Line Capability Customer Data