Why Alibaba Is Thinning Its Mid‑Platform and What It Means for Innovation
The article analyzes Alibaba's recent decision to dismantle and thin its mid‑platform, tracing its origins, evaluating its impact on business agility and innovation, and discussing why a leaner architecture suits combination‑style innovation while disruptive breakthroughs require a different approach.
According to insider information, Zhang Yong recently posted on Alibaba's internal network expressing dissatisfaction with the current mid‑platform, stating that the business development is too slow and the platform must become thinner, more agile, and faster.
Consequently, the debate concludes that Alibaba is completely dismantling its mid‑platform.
Background of the "Big Mid‑Platform, Small Front‑End" Strategy
In 2015, Zhang Yong introduced the "big mid‑platform, small front‑end" strategy. Five years later, he is now tearing down the very platform he built. This raises the question of whether the original strategy was a mistake.
The "big mid‑platform, small front‑end" model has become an industry standard, with many larger companies adopting similar architectures.
Zhang Yong gained fame with the "all‑in mobile" approach, launching the Taobao app that propelled Alibaba to a leading position in the mobile internet era.
The original goals of the mid‑platform were to create a unified technical architecture, product support system, data‑sharing platform, and security framework, thereby supporting diverse business models across the organization.
Undeniably, the mid‑platform has supported business growth over the past five years, contributing to increasingly stable systems during events like Double 11.
Limitations of the Mid‑Platform
After the "big mid‑platform, small front‑end" strategy, Alibaba introduced the "Five New" strategy: new retail, new manufacturing, new finance, new technology, and new energy, aiming for disruptive innovation rather than incremental improvements.
For example, the "new manufacturing" initiative is represented by Rhino Manufacturing, whose CEO was advised to establish an independent organization with its own business, technology, development, and product teams, because relying on the mid‑platform would be inefficient for a nascent business.
Similarly, the Taobao Special Edition project operates as an entirely independent unit to achieve deeper and faster innovation.
Is the mid‑platform incapable of supporting innovation? The answer is nuanced.
While the mid‑platform has enabled "combination innovation"—reusing standardized services such as product, inventory, user, payment, AI, and security to create new offerings like Hema Fresh—it struggles with "disruptive innovation," which requires breaking existing front‑end, mid‑, and back‑end structures.
An Alibaba mid‑platform architect explained that the goal now is to keep only the most abstract components in the platform, making it a thin layer that leverages accumulated generic capabilities to improve efficiency, reduce manpower, and free teams to focus on front‑end customization.
Future Outlook
The mid‑platform will continue to become thinner, more fragmented, and lighter—a trend consistent with earlier observations about platform fragmentation.
While the mid‑platform remains valuable for enhancing organizational efficiency and enabling combination‑style innovation, companies facing disruptive innovation challenges may need to move beyond it.
Enterprise leaders should avoid blindly following trends in digital transformation and instead adopt a long‑term, measured approach.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Programmer DD
A tinkering programmer and author of "Spring Cloud Microservices in Action"
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
