mobile architecture requirements
1. mobile applications require omni channel delivery
- netflix to smart phones , tablets , laptops , TVs, game consoles
2. mobile applications require a mix of native code and Web view to blend capabilities
3. mobile applications require dynamic composition of RESTful services.
- Services remixed from Google, facebook , Twitter , Twilio , Spotify, ... everyday
4. mobile applications require use of open source SaaS and PaaS
- OpenMeap now available on Openshift , and AWS MarketPlace
5. moblie applications require elastic IaaS
- Instagram adding 1M new customers in 13 hours
6. mobile applications require super-agile development
- AWS being released every 11.6 seconds
7. mobile applications require context awareness
- google mytracks records your path , speed , distance and elevation while you walk ,run or bike
8. mobile applications require predictive analytics
- google now attempts to get you just the right information at just the right time by predicting your actions
9. mobile services must be immediate visual and simple
- apple siri takes the user's voice commands and input
10. 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
11. mobile services must provide the roles of remote control , routing , and data/computation offloading for wearables and connectables
-Nike + FuelBand tracks your daily acitivies and calorie burned
12. shared infrastructure and multitenancy : learn to share
13. elasticity and scalability : all you can eat
14. On-demand self-service with simple interface : get it your self
15. consumption based pricing : pay per use
16. cloud computing model drives revolutionary changes in how solutions are designed , built , delivered , sourced and managed
Mobile context computing architecture
1. mobile services must be contextual
2. User's mobile context is recognized via sensors
- GPS , NFC , gyroscopes, barometer, accelerometers , microbolometer, magnetometer , chemical sensor ,...
3. User's mobile context is :
- Situational : current time, location, attitude, environmental conditions, travel speeds..
- Preferential : historical personal decisions
- Attitudinal : feelings and emotions implied by actions and logistics
4. User's mobile context is stateful
5. manage states in clients subject to device capacities
- allows 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
6. Use cloud to store and process the exploding amount of mobile contextual data, and to run predictive analytics.
댓글 없음:
댓글 쓰기