Mid-Platform (ZhongTai): Definition, Value, Types, and Implementation
This article explores the concept of the mid‑platform (ZhongTai) as an enterprise‑level capability‑reuse platform, explaining why companies adopt platformization, the distinction between front‑end, back‑end and mid‑platform, various types of mid‑platforms, and practical guidance for building and evaluating them.
The author reflects on a year‑long journey of dealing with concepts such as micro‑services, platformization, and the emerging notion of a "mid‑platform" (ZhongTai), which has caused both confusion and insight.
During a technical radar conference the author presented a talk titled "The Rise of Platform," describing how platforms have emerged globally across infrastructure, AI, and other domains, and their impact on developers and enterprises.
Initially the term "mid‑platform" seemed abstract, but the author realized it sits between the traditional front‑end (customer‑facing applications) and back‑end (core systems like ERP, finance, logistics). The mid‑platform aims to bridge the speed and flexibility gap between these layers.
Two fundamental questions are posed: why should enterprises adopt platformization, and why should they build a mid‑platform? The answer to the first is that in the internet era the user is the battlefield’s center; rapid user‑centric response is essential for survival and growth.
Platformization empowers companies to improve user response capability, enabling faster innovation and competitive advantage. Real‑world examples from Alibaba, Haier, and Huawei illustrate how large‑scale platforms support rapid iteration and user‑focused strategies.
The second question examines why existing back‑ends often cannot support the front‑end’s rapid innovation needs. Back‑ends focus on stability, compliance, and data integrity, leading to slow change cycles and high costs, while front‑ends demand agility. This mismatch creates a "gear‑speed" imbalance.
Gartner’s Pace‑Layered Application Strategy (Systems of Record, Systems of Differentiation, Systems of Innovation) provides a theoretical foundation for inserting a mid‑platform layer that offers the flexibility of innovation while maintaining the stability of core systems.
The mid‑platform is defined as an enterprise‑level capability‑reuse platform that can be technical, business, or organizational. Types discussed include:
Data‑business dual mid‑platform (Alibaba’s data and business platforms)
Mobile mid‑platform (built atop business and data platforms)
Technical mid‑platform (provides infrastructure and middleware abstractions)
R&D mid‑platform (supports development processes, CI/CD, quality management)
Organizational mid‑platform (acts as an internal venture and innovation hub)
All these serve the core purpose of extracting reusable capabilities from back‑ends and exposing them to front‑ends, thereby improving user response and scaling innovation.
The article emphasizes that the true value of a mid‑platform lies in its ability to enable reuse rather than merely eliminating duplication. Successful mid‑platforms focus on easy discoverability, self‑service consumption, and high‑level abstraction of business logic.
Finally, the author concludes that a mid‑platform is essentially an "enterprise‑level capability reuse platform," and that building one involves identifying, abstracting, and packaging capabilities so that multiple product teams can consume them efficiently, aligning technology with organizational goals.
Architects' Tech Alliance
Sharing project experiences, insights into cutting-edge architectures, focusing on cloud computing, microservices, big data, hyper-convergence, storage, data protection, artificial intelligence, industry practices and solutions.
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.