0 views collected around this technical thread.
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.
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 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.
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.