Kingdom KCBP/KCXP Evolution History: Twenty Years of Chinese Financial Middleware Innovation

#

Introduction: The Financial Middleware Foundation Behind China’s Securities Market

#

In China’s financial IT history, many critical technologies operate quietly behind the scenes.

They are rarely visible to end users, but they support every trading transaction.

Kingdom’s:

• KCBP (Kingdom Core Business Platform)
• KCXP (Kingdom Communication Exchange Platform)

are among the most representative examples.

Born during China’s transition from branch-based securities systems to centralized enterprise trading platforms, KCBP/KCXP evolved through:

Branch Trading Systems

↓

Centralized Securities Trading

↓

Enterprise Middleware Platform

↓

Cloud-Native Financial Architecture

Over more than twenty years, the technology evolved into:

KCBP/KCXP

↓

KROUTER/KADP

↓

KOCA Platform

↓

HARE/LDP Dual-Speed Architecture

1. Industry Background: From Branch Islands to Centralized Trading

#

1.1 The Branch-Based Era

#

During the 1990s, securities trading systems were mainly deployed independently at each brokerage branch.

The typical architecture was:

Branch Office

|

Local Trading Server

|

Local Database

Characteristics:

• Independent branch systems
• Data isolation
• High maintenance cost
• Limited scalability

As China’s securities market expanded, this architecture became insufficient.

2. The Centralized Trading Challenge (1998-2001)

#

2.1 The Need for Financial Middleware

#

Around 2000, securities companies began moving toward:

Nationwide centralized trading platforms

A new architecture required:

Trading Terminals

|

Communication Layer

|

Transaction Processing Layer

|

Database

At that time, the global financial industry mainly relied on:

• IBM CICS
• IBM MQ
• BEA Tuxedo

However:

• Licensing costs were high
• Technology was proprietary
• Domestic customization was limited

China’s financial software vendors started developing independent middleware platforms.

3. Birth of KCBP and KCXP: Domestic Financial Middleware Innovation

#

3.1 The Localization Mission

#

Kingdom started developing a new generation of securities transaction technology platforms:

• KCBP
• KCXP

The objective:

Build independent financial middleware with intellectual property ownership.

4. KCBP: Transaction Processing Middleware

#

4.1 Product Positioning

#

KCBP:

Kingdom Core Business Platform

Positioning:

A financial-grade transaction processing middleware platform.

Core responsibilities:

• Transaction integrity management
• Application scheduling
• Resource management
• Service execution control

Conceptually similar to:

IBM CICS

*

Securities Business Runtime Platform

4.2 LBM: Loadable Business Module Architecture

#

One of KCBP’s important design concepts was:

LBM (Loadable Business Module)

Architecture:

Client Application

|

KCBP Client

|

KCBP Server

|

LBM Business Modules

|

Database

Characteristics:

• Dynamic loading
• Dynamic unloading
• Modular business expansion

This resembles modern:

Plugin-based Architecture

5. KCXP: Communication Exchange Middleware

#

5.1 Product Positioning

#

KCXP:

Kingdom Communication Exchange Platform

Role:

Message-oriented middleware.

Responsibilities:

• Message transmission
• System communication
• Network abstraction

5.2 KCXP Architecture Model

#

Trading Applications

|

KCXP

|

KCBP Cluster

|

Database

KCXP solved communication differences among:

• Operating systems
• Network protocols
• Hardware platforms

6. KCBP + KCXP: The New Generation Centralized Trading Architecture

#

The architecture:

            Client

              |

            KCXP

              |

----------------------------

|            |             |

KCBP KCBP KCBP

              |

          Database

Advantages:

• High availability
• Horizontal scalability
• Centralized management
• Heterogeneous platform support

7. 2003: The Breakthrough of CITIC Securities and Guotai Junan

#

7.1 CITIC Securities Centralized Trading System

#

In 2003:

Kingdom successfully delivered the CITIC Securities centralized trading platform.

Technology stack:

IBM Mainframe/Server Platform

*

Unix

*

KCBP/KCXP

Significance:

It demonstrated that domestic middleware could support large-scale centralized securities trading.

7.2 Guotai Junan Distributed Centralized Trading System

#

Later in 2003:

Kingdom delivered another milestone:

x86 Servers

*

Windows Platform

*

Database Systems

*

KCBP/KCXP

Significance:

It proved that domestic middleware could support distributed enterprise-scale trading systems.

8. 2005-2013: Becoming a Core Securities Infrastructure Platform

#

As centralized trading became mainstream:

KCBP/KCXP continued evolving.

Cross-Platform Capability

#

Supported environments included:

Operating systems:

• Windows
• Linux
• Unix
• AIX
• ARM

Databases:

• Oracle
• IBM DB2
• SQL Server
• Sybase
• MySQL

Cluster Capability

#

KCBP clusters were built through KCXP messaging:

KCBP Cluster

|

KCXP Message Infrastructure

Providing:

• Dynamic scaling
• Load balancing
• High concurrency processing

9. 2013: Yu’e Bao and the Financial “De-IOE” Milestone

#

In 2013:

Kingdom participated in the technology construction of:

• Ant Financial
• Tianhong Asset Management
• Yu’e Bao

Core technologies:

KCBP

*

KCXP

*

Cloud Infrastructure

Yu’e Bao Phase II migrated its TA direct-sales system to the cloud.

The project demonstrated:

• Large-scale user support
• Fund transaction processing
• Enterprise system integration

It became one of China’s earliest major financial cloud transformation cases.

10. 2018-2020: Evolution Toward Enterprise Service Bus Architecture

#

As financial systems moved toward:

• Distributed architecture
• Service-oriented design
• Low-latency computing

KCBP/KCXP evolved further.

KROUTER

#

Evolution direction:

KCXP

↓

KROUTER

↓

Enterprise Service Bus

KADP

#

Evolution direction:

KCBP

↓

KADP

↓

Application Development Platform

11. KOCA Era: Integration with Cloud-Native Architecture

#

Around 2019:

Kingdom introduced:

KOCA Open Cloud-Native Architecture Platform

Architecture:

KOCA

├── HARE High-Speed Message Bus

├── LDP Low-Latency Platform

├── KCBP Transaction Middleware

├── KCXP Communication Middleware

├── Microservice Framework

└── Data Platform

12. The Dual-Speed Architecture Era

#

Modern financial systems require two different capabilities.

Fast Path: Low-Latency Trading

#

Designed for:

• Microsecond-level latency
• High-frequency scenarios

Technology:

HARE

*

LDP

Stable Path: Reliable Enterprise Transactions

#

Designed for:

• Reliability
• Long-term operation
• Cross-system integration

Technology:

KCBP

*

KCXP

Architecture:

         KOCA

           |

| |

HARE/LDP                 KCBP/KCXP

Low-latency              Reliable Core Systems

Trading                  Enterprise Transactions

13. Twenty-Year Evolution Timeline

#

14. The Technology Philosophy Behind KCBP/KCXP

#

Compared with rapid replacement approaches such as:

AS/AR

↓

CRES

↓

Light-JRES

Kingdom chose:

Long lifecycle evolutionary architecture.

Key principles:

• Avoid replacing stable core infrastructure
• Continuously improve capabilities
• Protect customer technology investment

Conclusion: Twenty Years Later, The Foundation Remains

#

The value of KCBP/KCXP is not only as middleware software.

It represents China’s financial software evolution:

Foreign Middleware Dependency

↓

Independent Financial Infrastructure

↓

Cloud-Native Financial Architecture

From:

• Securities centralized trading in 2003
• Yu’e Bao cloud transformation in 2013
• KOCA architecture today

KCBP/KCXP became one of the foundational technologies in China’s securities IT history.

The best infrastructure software is often invisible.

But every transaction depends on its reliability.

That is the meaning of the twenty-year evolution of KCBP/KCXP.