1、Ctrip MobileArchitecture Evolu2onEric Ye PuGong Liu Xiaolu HuangEric Ye CTRIP Senior Tech VPPuGong Liu Xiaolu Huang CTRIP Senior CTRIP Senior ArchitectureArchitectureAgenda•Demo •CtripMobile Architecture Overview •Ctrip Mobile Architecture Evolu2on –H5 decoupling –App decoupling –Te
2、s2ng Environments decoupling •Gains & Takeaways Demo•Demo Mobile Architecture 1.0 – Pain Points•Centralized mobile development Org: –Mismatched product roadmap between mobile team and business Team –Insufficient business domain knowledge –Product requirements piled up •Mobile Developm
3、ent Shortages –SPOF –Manual packaging and releasing –Insufficient tes2ng environment Mobile Architecture V1.0Mobile Architecture V2.0What was redesigned•H5 Decoupling –H5 Site/ H5 Service •App Decoupling –App / Mobile Service •Security Enhancement •Automa2on on tes2ng •Automa2on on
4、 releaseH5 Decoupling ‐ V1.0H5 Decoupling ‐ V2.0 (Front‐end)H5 Decoupling ‐ V2.0 (Back‐end)H5 Architecture Decoupled•Decoupling H5 Site and H5 Service•Mobile API Gateway –Service Rou2ng –Real 2me monitor –Bot Blocker –Rate limi2ng and Fuse off –Mul2ple IDC support Mobile App Decoup
6、end)Mobile App Architecture2.0 (Back‐end)Mobile App Decoupled•Dev teams decoupled –Framework dev team –Business dev (hotel) / business dev (flight) /… •API / services decoupled •Shared Mobile API Gateway •Automated mobile app release Tes2ng Environment 2.0 decoupledGains of Mobile
7、Architecture 2.0•Domain ownership clarified •Mobile App development speed •APP tes2ng decoupled •Mobile APP releasing efficiency •Robust architecture –Rate Limi2ng –Decoupled problems –Interfering each other is eliminatedAS of 2014/9 CTRIP APP is #1 Travel APP Sourced from CTCNN, 20