The article explains how financial systems define high concurrency by the TPS they can sustain, detailing the strict consistency, millisecond‑level response, and architectural patterns required for banking, securities, payment, and internet‑finance workloads.
The article analyzes how pursuing ever‑faster response times in financial services can amplify risk, cause cascading failures, and ultimately undermine competitiveness, arguing that true advantage lies in balanced risk management rather than sheer speed.
Facing limited visibility, routing, and security in traditional MQ-based financial systems, a company evaluated its needs for identity control, routing, auditing, low latency, scalability, ordering, and replay, and chose Apache Pulsar for its multi‑cluster, compute‑storage separation, pluggable authentication, rich API, and functions, outlining practical experiences and solutions.
This article provides a detailed walkthrough of bank core system architecture, covering its evolution, global overview, key modules such as customer information, account types, deposit and loan cores, payment and settlement, general ledger, card management, and batch processing, illustrated with diagrams and real‑world examples.
This comprehensive guide uses over 300 original hand‑drawn diagrams to explain payment system core businesses, payment and settlement flows, cross‑border acquiring, information and fund flows, account design, bookkeeping, reconciliation, and related concepts, providing a clear, entry‑level understanding of the entire payment ecosystem.
Facing a multi‑year, multi‑billion‑dollar core banking migration, the quality‑assurance team compressed a 3‑month testing window to two weeks by deploying risk‑driven test prioritisation, contract‑based end‑to‑end testing, layered automation, AI‑powered defect diagnosis and production‑traffic replay, delivering a dramatic efficiency leap while maintaining zero‑tolerance data accuracy.
This article examines how a ten‑year‑old financial accounting platform transformed from a monolithic design into a cloud‑native, micro‑service architecture that achieved massive scalability, high availability, and 24‑hour real‑time processing through distributed batch scheduling, elastic scaling, and intelligent fault‑tolerance.
This guide walks through designing and implementing a proactive, real‑time intrusion detection solution for financial systems by leveraging AWS CloudTrail to capture API activity and EventBridge to trigger alerts and automated responses, covering high‑risk IAM actions, network changes, and best‑practice rule configurations.
This article dissects the core principles and architectural patterns behind Chinese super‑payment platforms' settlement systems, covering transaction‑clear‑settlement flow, settlement modes, account models, system components, processing steps, and key performance indicators for handling trillions of yuan each day.
This article breaks down the essential terminology and underlying logic of bank accounts, covering basic concepts, classification by customer, function and content, structural hierarchies, account media, relationships, operational procedures, accounting ledgers, and risk‑control measures to build a comprehensive understanding of the banking account ecosystem.
This comprehensive guide walks through the fundamentals of building a reconciliation system, covering overview, data source management, transaction and fund reconciliation models, system architecture, data entity relationships, data acquisition, result handling, project design, engine control, error processing, and the strategic decision of reconciling before or after settlement, providing practical configurations, diagrams, and best‑practice recommendations for reliable financial operations.
The article reveals why most account designs get trapped by tightly coupling business transaction states with ledger entries, explains the pitfalls of updating massive historical records, and proposes a decoupled, pure‑account approach that treats each state change as an immutable accounting event.
This comprehensive guide explains the fundamentals of payment systems, covering definitions, development history, transaction flow, key terminology, account structures, payment tools, organizational roles, clearing and settlement mechanisms, and product classifications to help readers grasp the entire payment ecosystem.
The article shares a series of detailed payment‑clearing architecture diagrams that illustrate the full domestic payment ecosystem, its participants, settlement flows, and regulatory layers, inviting readers to explore each component and its interconnections.
This article provides a comprehensive, step‑by‑step explanation of China’s payment clearing ecosystem, covering the roles of transaction platforms, payment institutions, clearing organizations, banks, and the central bank, as well as the account structures, clearing models, real‑time settlement processes, and cross‑institution settlement mechanisms.
Implementing automated testing in financial systems faces numerous hurdles such as technical complexity, frequent requirement changes, unstable environments, compatibility issues, data sensitivity, script maintainability, skill gaps, limited resources, cross‑team collaboration, tool limitations, and strict security and compliance demands.
This article outlines a comprehensive automated testing framework for financial systems, covering goals, architecture, tools, processes, measurable outcomes, challenges, and improvement measures to boost test efficiency, coverage, defect detection, and system stability.
This article explains the concepts of bank reversal, error‑handling strategies by transaction date, the use of write‑off (抹账) and reversal (冲账) methods, red and blue corrections, and provides practical accounting entry examples for single‑sided and double‑sided ledger scenarios.
The article explains how to design a payment account system for e‑commerce, distinguishing payment accounts from login credentials, outlining key requirements such as transaction, accounting, reconciliation, risk control and credit, and detailing entity, account, and transaction models with attributes and control rules.
This article explains the foundational design of a payment system's account and accounting architecture, covering transaction models, account types, accounting entries, business processes, and the interaction between account, accounting, and settlement systems to ensure accurate financial tracking.
This article details how a major securities firm analyzed business stability, built a comprehensive stability engineering platform using chaos engineering, practiced extensive fault‑injection drills, and outlines future directions such as random‑scenario exercises, red‑blue battles, and AI‑driven risk detection.
Lufax completed a two‑year, zero‑downtime, 100% Oracle‑to‑MySQL migration across its entire financial platform, detailing the dual‑write strategy, fine‑grained batch switching, tool‑driven automation, and the resulting cost and operational benefits for over 45 million users and supporting critical transaction services.
This article presents a detailed case study of how a financial company adopted a micro‑frontend architecture to build a unified, low‑cost, and user‑friendly management platform, covering the motivations, design principles, technical components, deployment workflow, permission handling, and the resulting operational benefits.
ICBC's corporate wealth management platform, which supports trillion‑yuan assets for enterprise clients, has been migrated from a mainframe to a distributed OceanBase cluster, boosting high availability, ensuring business continuity, and cutting costs while maintaining performance and stability.
This article explores the layered redundancy of financial data centers, explaining hot and cold backups, multi‑site architectures, power supply safeguards, fire‑suppression systems, and why simply attacking a single component is unlikely to cripple services like Alipay.
The article explores how Alipay’s financial data is protected through multi‑site data centers, hot and cold backups, and disaster‑recovery mechanisms, explaining why destroying a single server—or even multiple facilities—won’t instantly erase users’ funds, and outlining the lengths required to truly cripple the system.
The article explains how financial platforms like Alipay protect user funds through multi‑site data centers, hot and cold backups, power redundancy, fire‑suppression systems, and strict location standards, showing why destroying a single server would not erase all stored money.
This article chronicles AutoHome’s five‑year journey of financial information system modernization, detailing the initial 2014 challenges, three development phases, the technical stack transitions, and the strategic outcomes that enabled unified finance operations and data‑driven management.
This article details more than fifty practical issues encountered when migrating financial applications from Oracle to PostgreSQL—including character sets, comment syntax, numeric precision, VARCHAR handling, sequence limits, type casting, operator overloading, and connectivity—while offering concrete solutions, code examples, and performance tips.
The article introduces a comparative test platform for financial core systems that automates regression testing of batch jobs, dramatically reducing test cycles from days to under one, while ensuring billing calculations remain accurate across evolving business scenarios.
This article details Ant Financial's multi‑year development of a comprehensive distributed transaction framework—including TCC, FMT, and XA models—designed to ensure financial‑grade consistency, high performance, and seamless cloud‑native integration for massive, latency‑sensitive payment and accounting services.
The article summarizes a 2017 BDTC conference talk by Ant Financial senior researcher Yang Zhenkun, detailing the challenges of traditional relational databases and presenting OceanBase's distributed, high‑availability, cost‑effective solutions for large‑scale financial systems.
The article reviews the historical development from closed‑architecture mainframes to open X86‑based small servers, analyzes Huawei's Kunlun and competing products, and discusses their RAS features, partitioning technologies, and suitability for high‑availability financial database workloads.
The 2005 Mizuho Securities “fat‑finger” incident, caused by a trader’s input error and a hidden bug in the Tokyo Stock Exchange’s Fujitsu‑built trading system, led to a ¥400 billion loss, sparking extensive litigation that highlighted responsibilities for software bugs, system testing, and operational risk management.
