DevOps & Apps - Building and Operating Successful Mobile Apps
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

DevOps & Apps - Building and Operating Successful Mobile Apps

on

  • 2,341 views

 

Statistics

Views

Total Views
2,341
Views on SlideShare
2,151
Embed Views
190

Actions

Likes
3
Downloads
37
Comments
1

7 Embeds 190

http://apigee.com 140
https://blog.apigee.com 29
http://mktg-dev.apigee.com 10
https://twitter.com 5
http://edit.apigee.net 3
http://edit.mktg.jupiter.apigee.net 2
http://mktg-new.local 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • <br /><iframe width="350" height="288" src="http://www.youtube.com/embed/pnRLihj9pX0?list=PL434D41A9FD27F1DA" frameborder="0"></iframe>
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Creative Commons Attribution-Share Alike 3.0 United States License
  • “Measurement”
  • “Measurement”Why are trying to be more accurate when you don’t even know what you are talking about?
  • Millions devices instead of thousands servers
  • Dviersity of Carriers / OS / Device models
  • Dviersity of Carriers / OS / Device models
  • Dviersity of Carriers / OS / Device models
  • How to improve it ?
  • Ask engineers/developers to add more metricsGet engineering involved with outages and troubleshooting issues

DevOps & Apps - Building and Operating Successful Mobile Apps Presentation Transcript

  • 1. DevOps and AppsBuilding and Operating SuccessfulMobile AppsApigee@apigeeBen Whaley@iAmTheWhaleyAlan Ho@karlunho
  • 2. groups.google.com/group/api-craft
  • 3. youtube.com/apigee
  • 4. slideshare.net/apigee
  • 5. @iAmTheWhaleyBen Whaley@karlunhoAlan Ho
  • 6. Agenda• The business model for mobile• DevOps in the context of mobile• Unique operational challenges• Addressing performance issues• Controlling Mobile configuration• What’s next for DevOps in this space?
  • 7. The landscape
  • 8. The freshness of mobile means that companies don’tyet care about revenue
  • 9. It’s a land grab for mobile apps
  • 10. Two most important things for business owners:- user engagement- reputation
  • 11. Performance and stability impact both
  • 12. DevOps can help with both
  • 13. HTML5 to native . . .small increase in speed . . .double number of Facebook posts read == double adrevenue
  • 14. Why is this business problem a DevOps problem?
  • 15. “You cannot improve what you cannot measure.”-Lord Kelvin
  • 16. Mobile DevOps vs.Back-end DevOps
  • 17. The code is running on a device
  • 18. Scale: controlling millions versus thousands
  • 19. Consistency in the cloud server environment does notapply in a mobile environment
  • 20. Diversity: Literally 100s of thousands of combinationsof Android OS / Device MODEL / Carriers
  • 21. Less control but you as the software developer areresponsible for quality
  • 22. Unique MobileChallenges
  • 23. Battery life
  • 24. Intermittent connectivity to the network
  • 25. Limitations imposed by the carriers and manufacturers
  • 26. Duopoly by Apple and Google
  • 27. Rapidly changing landscape for devices, apps and the OS
  • 28. Regulatory ImplicationsMany manufacturers and vendors support CISPA, forexample
  • 29. Wide gap among users in throughput, latency, dependingon network / carrier
  • 30. Communication with the end user
  • 31. Operating an app –Tips and Tricks
  • 32. Use the app! On many devices!
  • 33. Measuring the problem first
  • 34. Store metrics in system of choice(munin, graphite, ganglia, or apigee )identify trends
  • 35. System layer(load, memory, disk, standard operational metrics)
  • 36. Application layer(memory allocation, DB stats)
  • 37. API Layer(network latency, back-end availability)
  • 38. Response Time by Network Types
  • 39. Business layer# signups, #active users, # invites, social media sharing
  • 40. Monitor what is measured
  • 41. Engage key stakeholders
  • 42. Keep engineering involved from design throughoperation & management
  • 43. Eliminate barriers between groups
  • 44. Via HTTP expiry tag, set whether certain configurationremains valid or not
  • 45. Control configuration by model, carrier, platform,multitude of dynamic properties by which to changeconfiguration
  • 46. Changes and challengesto come
  • 47. More devices: The Internet of Things
  • 48. Mobile becomes the primary revenue provider instead ofweb
  • 49. Design the backend to be resilient across multipleproviders, and in a transparent way to the mobile device
  • 50. A short story about websockets . . .
  • 51. An app developer in the Philippines writes telco appsassuming a websocket is available . . .But some telcos do not support websockets . . .Negative reviews from users of the telco that doesn’tsupport it . . .Lesson: know the limitations of a carrier
  • 52. Explosion in data volume
  • 53. Geographic services increasingly important
  • 54. In Summary . . . mobile apps become a primary source of revenue success depends on engaging users and building a 5-star reputation performance and stability are critical DevOps is the centerpiece of an app’s success new DevOps challenges when code runs on a device measure all the things! (literally) the transformation is only beginning
  • 55. Questions
  • 56. groups.google.com/group/api-craft
  • 57. THANK YOUQuestions and ideas to:@iAmTheWhaley@karlunhogroups.google.com/group/api-craft