2013년 7월 18일 SW아키텍트대회에서 카이스트 박준성교수가 발표한 모바일 클라우드 아키텍처에 관한 강연자료

1. Mobile Cloud Architecture
Professor June Sung Park
KAIST
July 18, 2013

2. Mobile Applications Revolution
At a local outdoor farmers market set up in a
grassy field, I bought a bag of tomatoes from a
lady. She swipes my card on her Square mobile
card reader and I sign with my finger. My receipt
is in my inbox, and her cash is in the bank the
next day.
2

3. Mobile Applications Revolution
• Mobile Internet traffic has grown from 1% in 2009 to 13% in 2013.
• Over ½ of employees use personal devices at work.
• 13% of U.S. adults own a laptop, a smartphone and a tablet.
• By 2015, mobile app dev projects targeting smartphones and tables will outnumber
PC projects by 4:1.
• 41% of developers say they use PaaS to develop and deploy mobile applications.
• Mobile cloud market will explode to a $1T market by 2017.
• 75% of mobile cloud market is represented by enterprise users.
3

4. Mobile Applications Revolution
4
Mobile Network
Operators
Mobile Platform
Content Provider
Mobile
App Store
Mobile App
Developer
Mobile Handset
Manufacturer
Mobile User
ICT Service
Provider
Public
Cloud
Private
Cloud
Enterprise Mobility
Private
App Store

5. Mobile Applications Revolution
5

6. Mobile Architecture Requirements
• Mobile applications require omnichannel delivery.
– Netflix to smart phones, tablets, laptops, TVs, game consoles
• Mobile applications require a mix of native code and Web view to blend capabilities
of native platforms with the cross-platform portability of Web.
• Mobile applications require dynamic composition of RESTful services.
– Services remixed from Google, Facebook, Twitter, Twilio, Spotify,… everyday
6

7. Mobile Applications Architecture
7
Mobile Client
Mobile Apps
Mobile Web Native App
Mobile Platform
Applications
Application Framework
MEAP
Mobile Apps
Mobile Web Native App
Mobile Platform
Applications
Application Framework
RESTFUL and Web Services API (Façade)
Backend Applications
Process Orchestration
Infrastructure

8. Mobile Architecture Requirements
• Mobile applications require use of open source SaaS and PaaS .
– OpenMEAP now available on OpenShift, and AWS Marketplace
• Mobile applications require elastic IaaS.
– Instagram adding 1M new customers in 12 hours
• Mobile applications require super-agile development.
– AWS being released every 11.6 seconds
8

9. Mobile Cloud Architecture
9
BaaS
SaaS
PaaS
IaaS

10. Mobile Cloud Applications
10
On-Demand Mobile Services
 Hospitals such as New York-Presbyterian Hospital, Mayo Clinic,
Kaiser Permanente have developed a medical information platform
that provides patient data to both physicians and patients.
Companies developing new online, on-demand, mobile services as SaaS
for sales, logistics, healthcare, etc.
Mobile Streaming Services
 Walt Disney and Warner Bros both are developing cloud-based
systems to provide consumers with instant access to films and TV
shows via cable, computers and smart phones.
Companies developing new on-demand, streaming mobile services for
entertainment, surveillance, m-learning, etc.

11. Mobile Cloud Applications
11
Context-Aware Services
 Ford car software generates data on its location, speed, braking and
wiper use. It then correlates the data with live information from the
Web about traffic and weather, and sends messages about road
conditions via Twitter to other motorists in the same area.
Manufacturers embedding cloud-enabled services inside their products
to provide context-aware mobile services.
Big Data Analytics
 Marriott Hotel uses software that scans the public social cloud for
customer feedback and if a customer posts a complaint, the local
hotel is alerted to address the problem.
Companies using mobile clouds to store, analyze and visualize extreme
amounts of real-time unstructured data.

12. Mobile Architecture Requirements
• Mobile applications require context awareness.
– Google MyTracks records your path, speed, distance and
elevation while you walk, run or bike.
• Mobile applications require predictive analytics.
– Google Now attempts to get you just the right information
at just the right time by predicting your actions.
12

13. Mobile Context Computing Architecture
• Mobile services must be contextual.
• User’s mobile context is recognized via sensors.
– GPS, NFC, gyroscopes, barometer, accelerometers, microbolometer, magnetometer, chemical
sensor,…
• User’s mobile context is:
– Situational: current time, location, altitude, environmental conditions, travel speeds,…
– Preferential: historical personal decisions
– Attitudinal: feelings and emotions implied by actions and logistics
13

14. Mobile Context Computing Architecture
• User’s mobile context is stateful.
• Manage states in clients subject to device capacities.
– Allow pipes and filters and broker architecture mixed with MVC architecture for mobile clients
– Allows atomic services
– Allows stateless, asynchronous communications with clouds
– Allow load balancing and linear scale-out for IaaS
• Use clouds to store and process the exploding amount of mobile contextual data, and
to run predictive analytics.
14

15. Mobile Architecture Requirements
• Mobile services must be immediate, visual and simple.
– Apple Siri takes the user’s voice commands and input.
15

16. Touch-Free Client Architecture
• Shift of control from touch to voice and motion (e.g. Siri, Kinect)
• Heads-up display (e.g. Google Glasses)
– Without monopolizing the user’s attention, you will have to adapt to peripheral cues and the
addition of tactile and aural feedback and make sure that you don’t impair the user’s perception
of real-time space.
• On the contrary, touchwall computing with 84” screen will be broadly available soon.
• Modularized services APIs come in handy as user interface technology shifts.
16

17. Mobile Architecture Requirements
• Mobile services must overcome last-mile connectivity bottleneck of 3G/4G.
– Microsoft’s WhereStore prototype allows caching data to mobile devices from clouds to reduce
data unavailability and access latency.
• Mobile services must provide the roles of remote control, routing, and
data/computation offloading for wearables and connectables.
– Nike+ FuelBand tracks your daily activities and calorie burned.
17

18. Cloud-to-Mobile, Sensor-to-Mobile
Offloading Architecture
• Data and computation offloading from clouds
• In-memory database inside mobile devices
(e.g.. Memcached, Ehcache)
• Lightweight web server (e.g. Node.js, Nginx)
• Client/server cloudlet on WLAN
• P2P cloudlet on D2D network (e.g. Wi-Fi Direct)
– KAIST Smart 5G Cloudlet Research Center
18
Ad Hoc D2D Mobile Network
Distributed Parallel Computing
P2P Cloudlet Service

19. Cloud Architecture Requirements
19
Get it yourself
Shared
Infrastructure
and Multitenancy
Elasticity and
Scalability
On-demand
Self-service with
Simple Interface
Consumption-
Based Pricing
Learn to share
All you can eat Pay per use

20. Cloud Architecture Requirements
• Cloud computing model drives revolutionary changes in how solutions are designed,
built, delivered, sourced and managed.
20
Cloud Service Provider (External or Internal to Consumer Organization)
Cloud Service Consumer
Cloud Service
Infrastructure &
Offering
Cloud Service
Strategy
Cloud Service
Marketing and Sales
Cloud Service
Assurance & Billing
Cloud
Architecture
Cloud
Acquisition and
Implementation
Cloud
Requirement
Cloud
Operation

21. Cloud Enabling Technologies
• As is true of all profound IT changes, the apparent revolution of cloud computing is a
synergetic aggregation of evolutions in multiple, established technology directions.
21
Cloud Service
Infrastructure &
Offering
Cloud Service
Strategy
Cloud Service
Marketing and Sales
Cloud Service
Assurance & Billing
Cloud
Architecture
Cloud
Acquisition and
Implementation
Cloud
Requirement
Cloud
Operation
Infrastructure Virtualization
App Platform
SOA / WOA
Multitenancy Architecture
WAN optimization
Service Packaging
SLA
Web Marketing
Self-Service Portal
Real-Time Provisioning
ITIL Automation
Monitoring
Metering
Billing & Payment
Security
Business/IT Strategy
BPM
EA
SOA/WOA
Metadata Mgmt
Cloud Acquisition Policy
Fit/Gap Analysis
Cost/Benefit Analysis
App Composition Eng
ITIL
Monitoring

22. Cloud Architecture
22
Cloud Service Infrastructure
& Offering
Cloud Service Strategy
Cloud Service Marketing
and Sales
Cloud Service
Assurance & Billing
MEAP
BaaS

23. IaaS Architecture Requirements
23
Maturity of Infratructure Virtualization
ServiceEfficiencyandAgility
1.
Non-Virtualized
Data Center
2.
Server
Consolidation
through
Virtuaization
3.
Optimization of
Virtualized
Infrastructure
4.
Automation and
Orchestration of
Virtualized
Infrastructure,
5.
Self-Service
Provisioing,
Machine-Readable
SLA, Tenant-Aware
Service Delivery
and Usage-Based
Billing
IO IU IaaS

24. IaaS Architecture
24

25. PaaS Architecture Requirement
25
1995 2000 2005 2010
ESB
Integrated Service
Environment
BPM
RIA
Mobile Internet
Business
Rule Engine
Complex Event
Processing
Enterprise Mashup
Data Integration
Multitenancy
BAM
XTP
MOM
TP Monitor
RPC
Distributed
Component
Web Server
EAI
ETL
Portal
Application
Server
Component
Assembly
Application
Framework
IDE
+ + +
Tenant-Aware
Customization
B2B Gateway

26. PaaS Architecture
26
• Cloud Foundry is an open source PaaS allowing easy deployment of cloud
applications using Spring for Java developers, Rails and Sinatra for Ruby developers,
Node.js and other JVM frameworks including Grails.

27. PaaS Architecture
• CloudBees offers a Java Platform as a Service (PaaS) to build, run, and manage
enterprise Java applications.
27

28. PaaS Architecture
28
• Force.com multitenant architecture

29. SaaS Architecture Requirements
• Services accessible via user interface and “headless” APIs
• Apply WOA in frontend and SOA in backend
• Design multitenancy into the solution.
– Tenant-specific virtual application instances, SLAs, security, privacy,
– Tenant-aware customization: extensible data model, customizable GUI, customizable business
logic, customizable Workflow, internationalization
• Be sure to design business ‘Monetization’ into the solution.
– Multiple levels of services based upon functionality, SLA, etc.
29

30. SaaS Architecture
• IBM has developed a reference architecture for cloud services as an extension of the
SOA reference architecture.
30
SOA Cloud Service Architecture

31. SaaS Applications
31
EA-Based
ProcessIntegration
Process-OrchestratedCloud
Services
Online
Computing
(1970-80)
Client/Server
Computing
(1990-1995)
E-Business
(1995-2005)
IT
Standardization
ITModernization
SOA-Based
ProcessOrchestration
Mobile+Social+Cloud+
BigData
IT Dark Age
(1980-90)
Mobile Cloud
Computing
(2010-2015)
Technical Debt Payoff
(2005-2010)
Batch
Computing
(1950-1970)
Financial
Accounting
on Mainframe
(1972)
R/3
on C/S
(1992)
E-Business
Suite
(2002)
SOA:
SAP NetWeaver
Process Orchestration,
Enterprise Services
(2004)
2010s2000s1980s1970s1960s1950s 1990s
Process
Reengineering
ERPaaS:
Business ByDesign,
SAP Cloud
(for Sales, Service, Social Engagement,
Financials,Travel)
SAP Hana Cloud Integration,
Ariba, SuccessFactors
(2012)
• Evolution of SAP solutions

32. Enterprise Architecture Strategy
in Mobile Cloud Era
• Mobile cloud applications should be built based on standardized and
integrated business processes and data.
• Firms with silo apps, database instances and diverse infrastructure
need EA-based standardization and integration
to move fast in new technology adoption.
32
EA-Based
ProcessIntegration
Online
Computing
(1970-80)
Client/Server
Computing
(1990-1995)
E-Business
(1995-2005)
IT
Standardization
ITModernization
SOA-Based
ProcessOrchestration
Mobile+Social
+Cloud+BigData
IT Dark Age
(1980-90)
Mobile Cloud
Computing
(2010-2015)
Technical Debt Payoff
(2005-2010)
Batch
Computing
(1950-1970)
2010s2000s1980s1970s1960s1950s 1990s
Process-Orchestrated
CloudServices
Process
Reengineering

33. Enterprise Architecture Strategy
• Enterprise architecture, business process management, enterprise information
management and service-oriented architecture together enable firms to build a
stable digital foundation that is standardized, integrated, shared and yet agile.
33
J. W. Ross, P. Weill and D. C. Robertson, EnterpriseArchitectureas Strategy, 2006.
EA
EIM
SOA
BPM

34. Pace-Layered Architecture Strategy
• Apps move across layers as they mature.
• IT cannot succeed with explorative or exploitative apps on an unstable foundation.
• IT cannot skip maturity levels of business and IT.
34
Stable Digital
Foundation
Exploitative
Apps
Explorative
Apps
Business Process Management
Metadata Management
Enterprise Architecture
Service-Oriented Architecture
Process Orchestration
Enterprise Mobility
Social Business
Cloud Service Migration
Big Data Analytics
Case Management
Complex Event Processing
Event-Driven Architecture
Disruptive
Innovation
IT-Enabled
Business Transformation
Technical-Debt Payoff

35. Middle-Out Architecture Strategy
35
Mobile Devices, Wireless Sensors, 4G/5G, Social Networks, SaaS, PaaS, IaaS, Hadoop,
In-Memory Database, Data Science, Software-Defined Network, M2M, IoT,…
Stable
Business Services
and Metadata
Emerging
Technologies
Business
Innovations

36. Q&A
June.park@kaist.ac.kr
https://www.facebook.com/JP.Institute.of.Software
http://jpinstituteofsoftware.wordpress.com/