DevOps & Apps - Building and Operating Successful Mobile Apps

2,883 views

Published on

Published in: Technology, Business
1 Comment
4 Likes
Statistics
Notes
No Downloads
Views
Total views
2,883
On SlideShare
0
From Embeds
0
Number of Embeds
392
Actions
Shares
0
Downloads
50
Comments
1
Likes
4
Embeds 0
No embeds

No notes for slide
  • 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

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

    ×