Ctrip’s Technical Transformation (2011‑2014): Architecture, Mobile Strategy, and Organizational Change

In late 2011 Ctrip’s traffic composition was Online 25%, Offline 75% and Mobile was almost ignored; by the end of the following year the figures had changed to Online 35%, Offline 15% and Mobile 50%.

The talk, organized by BT Media and CSDN, recounts the experience of Ye Yaming, senior VP of technology at Ctrip, who joined the company at the end of 2011 after stints at Yahoo and eBay where he built eBay China’s R&D center.

Ctrip, proud of its call‑center technology, expanded to 16 business units over the past two years, each with its own development, product, and service teams, creating a relatively self‑contained structure.

When Ye joined, the main issues were a lagging online share (only 25%) and a lack of mobile focus, while the call‑center staff (about 12,000) was already a market leader in China.

Ye emphasized that Ctrip’s product was a tool rather than a user‑experience‑driven service, and that the organization needed a clear “prescription” from the CEO to turn ideas into concrete results.

Performance targets such as page response times of 200‑500 ms were discussed, noting that Chinese internet conditions often made even sub‑second responses feel slow, and that achieving a 1‑second perception threshold required architectural improvements.

By the end of 2013 Ctrip decided to invest heavily in wireless (mobile) development, creating a separate wireless business unit and aiming for a combined Online + Mobile share of about 70%.

In early 2014 new challenges emerged: six new business lines added in 2013, wireless development lagging behind web, weak wireless payment integration, and increasing complexity as more features and developers were added, leading to bottlenecks.

To address these issues Ctrip re‑organized: the wireless team was split across the 16 business units, each now responsible for its own wireless product, with clear KPIs for Online, Offline and Mobile shares compared against competitors such as Dianping.

Key best‑practice takeaways presented were:

Architecture: the most effective architect is the CEO; distinguish between architectural and organizational problems.

Technical architecture should be simple yet capable of supporting ten‑fold business growth.

Every engineer should adopt a “wireless mindset”.

Decentralize ownership: each business team manages its own wireless product and KPI.

Cultivate an engineer culture that respects release schedules regardless of individual obstacles.

Transformation steps included “Everything Decoupled”: eliminating inter‑business coupling by providing separate databases, deployment, testing, and cost centers for each line (e.g., flights, hotels, trains), thereby preventing shared‑resource bottlenecks.

On the app side, Ctrip focused on payload reduction, traffic monitoring per business line, hybrid frameworks, user‑experience metrics (client‑side page load time), and significant improvements in wireless payment success rates (+10 %).

They also built a custom Push Server using Go, developed wireless voice search, and optimized request latency and real‑time monitoring.

The app homepage was redesigned for rapid iteration, responsive design across iOS 4‑6 devices, and adaptive design allowing a single codebase to run on many devices, making Ctrip’s travel app the market leader.

(Source: Speech by Ye Yaming, Senior VP of Technology, Ctrip, at the BT Technology Business 500 Forum, compiled by Zhang Yuting)