本文是2013年11月在Mobile@Scale大会上Linkedin的分享的一个备注,比较乱,讲了Linkedin一路以来移动开发的架构优化之路,原视频在YouTube上,想看的自备梯子

2012 Q1

Screen Shot 2014-06-20 at 1.18.09 AM

Screen Shot 2014-06-20 at 1.19.10 AM

Screen Shot 2014-06-20 at 1.19.51 AM

  • Flag Based Feature Development: http://code.flickr.net/2009/12/02/flipping-out/

Screen Shot 2014-06-20 at 1.20.27 AM

  • Every Checkin都要求95%以上的Routes Testing Coverage
  • Test跑Phone Server上,不涉及UI测试
  • VCR相当于playback Linkedin API的返回值,capture & callback

Screen Shot 2014-06-20 at 1.22.25 AM

Screen Shot 2014-06-20 at 1.29.06 AM

Screen Shot 2014-06-20 at 1.12.17 AM

2012 Q3

Screen Shot 2014-06-20 at 1.29.55 AM

Screen Shot 2014-06-20 at 1.30.08 AM

  • HTML5 cause 3%-4% crash rate

Screen Shot 2014-06-20 at 12.33.52 AM

Present – 2013

  • 5 apps

Screen Shot 2014-06-20 at 12.41.02 AM

Screen Shot 2014-06-20 at 12.43.16 AM

Screen Shot 2014-06-20 at 12.50.26 AM

  • Action Metric Coverage: Action是指用户交互的行为,track用户所有的交互的行为
  • Top Metric Flow Coverage: 从Action Metric中选出用户交互最频繁的操作flow,自动化cover这些flow以后就可以轻松搞定发布问题

Screen Shot 2014-06-20 at 12.51.32 AM

  • Train Model: 固定时间发布,功能点赶得上就赶,赶不上就下一个固定时间再发,功能用feature flag来控制

Screen Shot 2014-06-20 at 1.04.28 AM

Screen Shot 2014-06-20 at 1.11.38 AM

Screen Shot 2014-06-20 at 1.12.17 AM

Architecture In The Future

Screen Shot 2014-06-20 at 1.14.43 AM

Screen Shot 2014-06-20 at 1.16.45 AM