↓ Skip to main content
vtoollab
  1. Posts/

The History of Early IOE Architecture in Financial Industry: How IBM, Oracle and EMC Built the Foundation of Modern Banking Systems

1170 words·
Financial IT History Enterprise Architecture IOE IBM Oracle EMC Mainframe Tuxedo Financial Architecture Banking IT Securities IT
Table of Contents

The History of Early IOE Architecture in Financial Industry: How IBM, Oracle and EMC Built the Foundation of Modern Banking Systems
#

Introduction: What Was IOE Architecture?
#

In financial IT history, the term IOE usually refers to:


I = IBM

O = Oracle

E = EMC

It represents the enterprise infrastructure stack that dominated banks, securities firms, and insurance companies from the 1990s to the early 2010s.

The classic financial architecture looked like:

      Client

        |

Application Server

        |

Transaction Middleware

        |

      Oracle

        |

  EMC Storage

        |

  IBM Server

For nearly two decades, this architecture became the foundation of global financial computing.

1. Why Did Financial Industry Need IOE?
#

1.1 Financial Systems Are Different
#

A normal Internet application can tolerate:

  • temporary failures
  • retries
  • partial data loss

Financial systems cannot.

A stock trading transaction:


Customer places order
↓


Cash verification
↓


Order creation
↓


Exchange submission
↓


Trade confirmation

Any inconsistency may cause:

  • financial loss
  • regulatory problems
  • incorrect settlement

Therefore financial institutions require:

  • extreme reliability
  • transaction consistency
  • high concurrency
  • disaster recovery

2. IBM: The Foundation of Financial Computing
#

2.1 The Mainframe Era
#

From the 1970s to 1990s:

Most banking systems were built on:


IBM Mainframe

Typical architecture:


Terminal

|

IBM Mainframe

|

CICS

|

DB2

IBM provided a complete ecosystem:

  • hardware
  • operating system
  • transaction processing platform
  • database

3. IBM CICS: The Birth of Financial Transaction Processing
#

CICS:

(Customer Information Control System)

was not a database.

It was a transaction processing platform.

Its responsibilities:


Transaction Request
↓


Transaction Management
↓


Program Scheduling
↓


Resource Control

Example:

ATM withdrawal:


ATM Request

↓


CICS

↓


Account Verification

↓


Balance Update

↓


DB2 Commit

CICS changed financial software development:

Business transactions became managed system resources instead of ordinary application programs.

4. Oracle: The Database Foundation of Open Systems
#

4.1 The Unix + Oracle Era
#

During the 1990s:

Financial systems gradually moved from:


Mainframe

↓


Unix Servers

The new architecture became:


Unix

*

Oracle Database

*

Middleware

This became the standard enterprise architecture.

5. Oracle’s Role in Financial Systems
#

Oracle provided:

Data Management
#

Example:

Customer accounts:

ACCOUNT_TABLE

Trading orders:

ORDER_TABLE

Cash balance:

BALANCE_TABLE

Transaction Consistency
#

Example:

Bank transfer:

BEGIN;

UPDATE ACCOUNT_A;

UPDATE ACCOUNT_B;

COMMIT;

Oracle guaranteed:

  • Atomicity
  • Consistency
  • Isolation
  • Durability

(ACID)

However:

Oracle did not solve:

  • request routing
  • application scheduling
  • distributed transaction coordination

This created the need for middleware.

6. BEA Tuxedo: The Middleware Bridge Between Applications and Databases
#

During the 1990s:

The typical financial architecture became:

Client

  |

BEA Tuxedo

  |

Oracle Database

Tuxedo solved several critical problems.

6.1 Distributed Transactions
#

Financial systems often involved multiple services:

Trading System

+

Account System

+

Settlement System

Middleware coordinated transactions across different resources.

6.2 Application Server Model
#

Instead of:

Client

   |

Database

The architecture became:

Client

   |

Middleware

   |

Business Services

   |

Database

Clients called business functions:

BUY_STOCK()

SELL_STOCK()

TRANSFER_MONEY()

Tuxedo located and executed the correct service.

6.3 High Concurrency Processing
#

Typical model:

              Tuxedo

          /     |      \

     Server Server Server

Thousands of requests could be processed simultaneously.

7. EMC: Enterprise Storage Backbone
#

Financial institutions care about one thing above all:

Data safety.

EMC storage provided:

Application

     |

Database

     |

EMC SAN Storage

Capabilities:

  • RAID protection
  • redundant controllers
  • replication
  • disaster recovery

8. Formation of IOE Architecture in Chinese Financial Industry
#

Stage One: Banking Core Systems in the 1990s
#

Typical architecture:

IBM Mainframe

+

CICS

+

DB2

Used for:

  • banking counters
  • clearing
  • credit cards

Stage Two: Securities Centralized Trading Era
#

Before 2000:

Securities firms used branch-based systems:

Shanghai Branch

Database


Beijing Branch

Database

Every branch was an isolated system.

After 2000:

Centralized trading became necessary:

Nationwide Investors

          |

Central Trading Platform

          |

Database Center

This required:

  • middleware
  • message communication
  • clustering
  • transaction processing

9. Typical IOE Architecture Around 2000
#

A securities company architecture:

Client

 |

BEA Tuxedo

 |

Oracle

 |

EMC

 |

IBM Unix Server

This was the mainstream financial architecture.

10. Why Did Domestic Middleware Appear?
#

A key question:

Hardware could be purchased.

Database could be purchased.

But the transaction execution platform was the core capability.

At that time:

Foreign Middleware

        +

Oracle Database

controlled the most critical layer.

Therefore Chinese financial IT companies started developing their own middleware platforms.

11. Birth of Domestic Financial Middleware
#

Kingdom KCBP / KCXP
#

Architecture:

Client

 |

KCXP

 |

KCBP

 |

Oracle Database

Positioning:

  • KCXP: communication/message middleware
  • KCBP: transaction processing middleware

Comparable technologies:

IBM MQ

+

CICS/Tuxedo

Hundsun AS / AR
#

Architecture:

Client

 |

AR Router

 |

AS Application Server

 |

Database

Concept:

  • AR handled routing
  • AS handled business execution

Comparable to:

Application Router

+

Transaction Server

12. Why Did Financial Industry Start Moving Away From IOE?
#

12.1 Cost
#

Traditional IOE systems were expensive:

  • proprietary servers
  • commercial databases
  • enterprise storage

12.2 Scalability
#

Traditional architecture focused on vertical scaling:

Bigger IBM Server

But Internet finance required:

Thousands of commodity servers

12.3 Cloud Computing
#

Companies proved that distributed systems could replace expensive proprietary platforms.

13. Yu’e Bao and the Financial “De-IOE” Movement
#

2013 became a landmark year.

Alibaba and Tianhong Fund launched Yu’e Bao.

The architecture moved toward:

Cloud Infrastructure

+

Distributed Architecture

+

Domestic Middleware

Kingdom KCBP/KCXP played an important role in:

  • TA system integration
  • transaction processing
  • system communication

It became one of the representative cases of financial de-IOE architecture.

14. The Architecture After IOE
#

Modern financial architecture:

Cloud Platform

        |

Microservices

        |

Distributed Middleware

        |

Distributed Database

        |

Cloud Storage

However, IOE-era principles remain:

  • transaction integrity
  • reliability
  • consistency
  • disaster recovery

15. Historical Meaning of IOE
#

IOE was more than three vendors.

It represented a complete financial computing philosophy.

IBM
#

Solved:

How to execute financial transactions reliably

Oracle
#

Solved:

How to store and manage financial data consistently

EMC
#

Solved:

How to protect mission-critical data

Together they created:

Enterprise Financial Computing Model

16. From IOE to Financial Technology Independence
#

IOE was once the most advanced financial architecture in the world.

It enabled Chinese financial institutions to achieve:

  • informatization
  • centralization
  • enterprise-scale operation

However, as financial systems became larger, the industry realized:

Core financial infrastructure cannot permanently depend on external technology stacks.

The evolution became:

IBM + Oracle + EMC

+

Tuxedo


        ↓


Domestic Servers

+

Domestic Databases

+

KCBP/KCXP

+

CRES/JRES

+

Cloud Native Platforms

This was not a simple replacement.

It was a transition from:

Using global financial technology

to:

Building independent financial computing capabilities

Financial Architecture Evolution Timeline
#

1970-1990

IBM Mainframe

CICS

DB2


        ↓


1990-2010

Unix

Oracle

BEA Tuxedo

EMC


        ↓


2000-2020

Domestic Middleware

KCBP/KCXP

AS/AR

CRES


        ↓


2020+

Cloud Native

Microservices

Distributed Middleware

AI Infrastructure

Conclusion
#

The IOE era was one of the most important chapters in financial IT history.

IBM, Oracle, EMC, and middleware platforms such as Tuxedo created the foundation of modern banking and securities systems.

The rise of domestic middleware such as:

  • Kingdom KCBP/KCXP
  • Hundsun AS/AR
  • CRES
  • JRES

was not simply about replacing foreign products.

It represented a deeper transformation:

from consuming financial infrastructure technology to mastering the core platforms that run financial systems.

Related