What Is a Mid‑Platform (中台) and How Does It Transform Enterprise Architecture?

Mid‑platform (中台) has become a hot concept in China over the past two years. In late 2015 Alibaba Group announced a comprehensive middle‑platform strategy, building a "big middle‑platform, small front‑platform" organizational and business mechanism for the DT era. By separating product‑technology and data‑operation capabilities from the front‑end, a middle‑platform can independently serve the front‑end, making front‑end business more streamlined, agile, and responsive to rapid market changes.

The middle‑platform generally has three functional attributes:

Regulator between front‑end and back‑end : aggregates reusable data, experience, and practices into a highly cohesive, loosely coupled capability platform, accelerating the conversion from raw resources to value‑creating services.

Accelerator for front‑end business : packages raw back‑end resources into a common product or service, allowing new business development to directly consume these services.

Stabilizer for back‑end systems : extracts frequently changing back‑end capabilities that support the front‑end, exposing them via various interfaces to provide stable and reliable services.

The author first encountered the middle‑platform concept during a project with Alibaba Cloud and, after a year of involvement in related projects, attempts a simple overview.

1. What Is a Middle‑Platform?

There is no single unified definition for a middle‑platform. Enterprise architecture frameworks such as Zachman and TOGAF describe architecture from four perspectives: business architecture, information‑system architecture (including data and application architecture), technical architecture, and governance architecture. Business architecture is the prerequisite for the other layers and ultimately serves business goals such as solving efficiency problems, reducing costs, controlling risks, and discovering new opportunities.

From a business‑architecture viewpoint, the middle‑platform is a "business middle‑platform". By extracting common business requirements, it decouples business from front‑ and back‑end, making the business lighter and more agile.

From an information‑system‑architecture viewpoint, it consists of an "application middle‑platform" and a "data middle‑platform". The application middle‑platform extracts and integrates reusable basic services from application systems, turning them into standardized core capabilities for upper‑level applications. The data middle‑platform handles data collection, storage, computation, and processing, forming a unified data resource center that provides consistent data services.

From a technical‑architecture viewpoint, it is a "technical middle‑platform" that offers reusable infrastructure capabilities. By integrating and encapsulating technical components, it hides implementation details and provides simple, consistent, and easy‑to‑use technical interfaces, helping front‑end and business/data middle‑platforms build quickly.

From a governance‑architecture viewpoint, it is an "organizational middle‑platform". Successful IT application requires an evolving organizational structure that supports the middle‑platform model, such as government service halls, Alibaba’s shared‑business units, or telecom service centers.

Typical architecture of an enterprise middle‑platform.

2. What Are Front‑End and Back‑End?

Since a middle‑platform exists, front‑end and back‑end also exist. Front‑end can be classified from two dimensions: IT‑architecture and business‑dimension.

From the IT‑architecture dimension

Front‑end: Systems directly used by external or internal end users, such as corporate websites, WeChat mini‑programs, mobile apps, internal OA, CRM, finance systems, etc.

Back‑end: The typical back‑office of an application system, used by administrators to provide user, permission, configuration, maintenance, operation, logging, and security functions. After adopting a middle‑platform strategy, these functions can be extracted to the middle‑platform and offered as unified capabilities to multiple applications.

From the business perspective, the business middle‑platform extracts, consolidates, and integrates reusable resources from application systems, which themselves consist of front‑end and back‑end components. The normal operation of an application system requires back‑end support, and the business middle‑platform integrates reusable common capabilities of both front‑end and back‑end, as shown in the diagram below:

By extracting and integrating common capabilities of front‑ and back‑end, a structure of large middle‑platform, small front‑end, and small back‑end emerges, where the front‑end relies on the capabilities provided by the middle‑ and back‑end to serve end users.

From the business dimension

Front‑end: Systems used by external end users, such as corporate websites, WeChat mini‑programs, mobile apps, etc.

Back‑end: Systems used by internal users, typically supporting daily operations and management, such as finance, production, warehousing, customer, procurement, marketing, and internal collaboration tools.

In this dimension, many domestic enterprises have very weak front‑end capabilities, often limited to a website or public account, lacking online services or marketing. Achieving comprehensive digital transformation therefore requires a long journey.

In recent years, the government has vigorously promoted "Internet+" public services. The author participated in Hangzhou’s “One‑Window Acceptance, Four‑End Collaboration” platform, a good practice of the "small front‑end, big middle‑platform" model. The platform consists of a "government middle‑platform" plus four "business front‑ends". The middle‑platform provides unified items, scenarios, materials, and forms, allowing the front‑ends to focus on business implementation and user experience, making them "small but beautiful" and enabling rapid trial‑and‑error and iteration.

· The four ends refer to personal fixed‑end (PC), personal mobile‑end (phone), hall self‑service terminal, and hall window terminal. · Hangzhou’s platform, based on big data, facial recognition, and other technologies, connects the four ends, establishes standardized item, scenario, and "one‑item" package libraries, forming a "thousand‑person‑one‑face" service map that provides personalized, precise, scenario‑based, and package services for citizens and enterprises, promoting the "most‑once‑run" reform at the grassroots level, deepening "near‑by‑service", and improving satisfaction.

3. Challenges and Recommendations for Middle‑Platform Implementation

Middle‑platform staff often do not interact with the market or users, lacking demand insight. With limited resources, it is difficult for the middle‑platform to evaluate the value of multiple projects and make trade‑offs. To extend the middle‑platform’s reach and understand business essence better, a team that knows both business and technology is needed.

The author’s approach is to let product personnel of the middle‑platform also be responsible for a portion of front‑end business, encouraging them to engage with market and users, continuously gather front‑end feedback, and iterate the middle‑platform capabilities. This, however, requires organizational governance guarantees.

4. Advantages of Implementing a Middle‑Platform Strategy

In summary, the advantages of adopting a middle‑platform strategy include:

Service reuse: Realizes the core value of SOA, where loosely coupled services enable business reuse.

Service evolution: As new businesses join, shared services evolve from thin functions to robust, powerful assets, becoming valuable IT assets.

Data accumulation: All business data accumulates in the same middle‑platform, unlocking big‑data value.

Rapid response: Faster composition of shared services to meet new business needs.

Cost reduction: New businesses can avoid duplicate development, reducing personnel costs.

Efficiency improvement: Developers focus on specific domains, leading to faster development and easier maintenance.

References

^党建中台研究与实践 https://mp.weixin.qq.com/s/AbkVOQPDbPId32CMgBMO-A

^阿里中台战略是个伪命题 https://www.iyiou.com/p/104526.html

^白话中台战略 http://www.sohu.com/a/319181062_99979179

Source: https://zhuanlan.zhihu.com/p/84137455