Tagged articles
reconciliation
50 articles · Page 1 of 1
This article explores how React's key prop works internally, tracing its path from JSX to ReactElement and Fiber, and detailing the three-phase reconciliation algorithm that matches old and new nodes during list updates, with source code examples from React v19.2.8.
FiberReactReactElement
0 likes · 24 min read

This article details a production-grade member points and growth system built on Spring Boot, covering account modeling with ledger tables, batch-based expiration, FIFO deduction, idempotency keys, freeze/unfreeze flows, high-concurrency Redis pre-deduction with async DB persistence, anti-fraud layers, and a three-equation reconciliation framework with automated repair.
Anti-FraudDatabase DesignIdempotency
0 likes · 34 min read

This article walks through implementing a financial-grade double-entry bookkeeping system using Spring Boot 3, MyBatis, and MySQL, covering domain modeling with immutable entries and derived balances, a posting engine with idempotency and debit-credit validation, balance calculation via snapshots and incremental deltas, end-of-day trial balance verification, cross-system reconciliation, and production concerns like precision handling, sharding strategies, and hot-account mitigation.
IdempotencyMyBatisMySQL
0 likes · 36 min read

This article presents a production-grade design for handling long-running, preemptible worker tasks in Go and PostgreSQL, covering lease protocols, fencing tokens, outbox patterns, and side-effect reconciliation to prevent stale workers from corrupting state or duplicating external operations.
FencingGoIdempotency
0 likes · 37 min read

This article guides backend engineers through building a production-ready Kubernetes Operator in Go for reliable microservice auto-scaling, covering capacity modeling, CRD design, reconciliation patterns, error handling, testing strategies, and phased deployment to replace fragile scripting with robust control loops.
Auto ScalingCRDController-runtime
0 likes · 50 min read

This article explains why automatic retries after agent timeouts can duplicate business actions, and details how to distinguish call failures from executed side effects, implement execution-side idempotency guarantees, reconcile using original action identifiers, and define safe recovery rules with human escalation when outcomes remain unknown.
Agent SystemsIdempotencydistributed systems
0 likes · 17 min read

This article analyzes four patterns for keeping Elasticsearch synchronized with MySQL — synchronous dual-write, message-queue async, CDC via Canal/binlog, and scheduled reconciliation — explaining why CDC with version-based deduplication and periodic checksums is the production-grade choice for eventual consistency at scale.
CDCCanalData Consistency
0 likes · 16 min read

This article walks through designing a points system architecture, starting from a concrete scenario of consuming 80 points across two batches with retries and refunds, covering data models, idempotency keys, local transactions, cache-aside, event-driven reconciliation, scaling strategies, and evolutionary deployment phases.
Cache AsideIdempotencyPoints System
0 likes · 27 min read

This article explores data quality challenges in real-time data warehouses, covering timing agreements for late-arriving data, reconciliation techniques using Flink and Paimon, SQL-based checking strategies, alerting with actionable details, and iterative quality validation processes.
CDCDorisFlink
0 likes · 15 min read

In high‑throughput wallet systems, reconciliation—covering internal balance validation, channel‑level matching, and controlled auto‑repair—acts as the final safeguard against fund discrepancies caused by lost callbacks, out‑of‑order events, duplicate entries, or concurrency conflicts, ensuring financial safety even with billions of daily transactions.
auto-repairbalance-validationdistributed systems
0 likes · 33 min read

The article explains that a production‑grade wallet must store balance snapshots instead of summing transaction flows, using double‑entry bookkeeping, ACID guarantees, idempotent request handling, outbox messaging, sharding, and comprehensive reconciliation to ensure correctness and high‑throughput under heavy concurrency.
IdempotencyOutbox PatternSharding
0 likes · 43 min read

The article walks through the evolution of a flash‑sale inventory‑deduction system, starting with simple database row‑locking SQL, exposing its scalability limits, and progressively adding transaction trimming, Redis pre‑deduction, Lua atomic scripts, async pipelines, idempotency, reconciliation and robust engineering practices to handle extreme concurrency.
AsyncProcessingHighConcurrencyIdempotency
0 likes · 40 min read

The article examines why payment callbacks that arrive later than order cancellations cause money‑in‑order‑canceled anomalies, outlines the three core eventual‑consistency problems—message ordering, duplicate consumption, and message loss—and presents a complete engineering solution using business idempotency keys, a transactional outbox, state‑machine handling, and reconciliation compensation.
IdempotencyKafkaTransactional Outbox
0 likes · 35 min read


Niu LiuAug 12, 2026 · Backend Development
This article details a production-grade WeChat Pay service provider integration for multi-store, multi-entity scenarios, covering domain modeling, versioned payment routing, sub-merchant onboarding state machines, cashier configuration layers, callback verification, refund snapshot isolation, three-level reconciliation, and a 10-item launch checklist.
APIv3Cashier ConfigurationIdempotency
0 likes · 28 min read

This article explains why a payment system is more than a simple SDK integration, presents a four‑layer architecture (access, state, event, governance), details state machines, idempotent callbacks, outbox pattern, reconciliation, high‑concurrency handling, observability, security, and provides Java code examples for integrating Alipay and WeChat across all channels.
AlipayIdempotencyJava
0 likes · 29 min read

The article outlines a five‑layer accounting architecture and detailed processes—including account sub‑systems, posting and freezing rules, sub‑account splitting, daily‑cut scheduling, and reconciliation mechanisms—that enable a global payment institution to manage multi‑currency, multi‑timezone, and multi‑regulatory requirements with a single account.
accounting architecturedaily cutglobal payments
0 likes · 18 min read

This article reviews the end‑to‑end design of a payment platform that handles 500,000 daily orders, detailing the three‑layer gateway‑orchestration‑base architecture, independent channel services, reconciliation mechanisms, and how business constraints drive each architectural decision.
Gatewayhigh concurrencymicroservices
0 likes · 15 min read

An incident where a forged free‑card callback corrupted order status reveals the need for daily cross‑system reconciliation, and the article outlines a 20‑part series that details the architecture, design decisions, multi‑channel handling, risk control, and implementation of a production‑grade payment system serving over a hundred million users.
JavaRisk ControlSpring Boot
0 likes · 17 min read

This guide condenses essential accounting knowledge for payment product managers, covering the accounting equation, its five practical uses, the accounting cycle, ledger and voucher structures, subject‑account relationships, double‑entry rules, trial balance, reconciliation, closing procedures, financial statements, and concrete journal examples for common transactions.
Double EntryTrial Balanceaccounting
0 likes · 14 min read

This article demystifies the hidden fund‑management layer behind online payments, explaining reserve‑account handling, internal and virtual accounts, settlement, reconciliation, bookkeeping, accounting, and the added complexities of cross‑border payments such as multi‑currency, liquidity, and regulatory challenges.
Liquidityaccountingcross‑border
0 likes · 23 min read

This article explains the fundamentals of financial reconciliation, outlines the two‑step reconciliation process, and details a streaming reconciliation architecture capable of handling 30 billion USD per hour (≈27 777 TPS) with high concurrency, distributed parsing, and efficient result aggregation.
Financialdistributed-systemshigh-throughput
0 likes · 8 min read

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.
Data Managementerror handlingfinancial systems
0 likes · 37 min read

This article explains how major payment institutions ensure the accuracy of tens of millions of daily transactions and billions of dollars by using a four‑segment data model, three verification groups, error classification, and extensible data coding to achieve reliable settlement and accounting.
Data ModelingOperationsaccounting
0 likes · 6 min read

This article explains the concepts, models, architecture, data management, project configuration, engine design, and error‑handling procedures needed to implement an automated, systematic reconciliation system that can handle large‑scale online transaction volumes with high accuracy and efficiency.
automationdata pipelineerror handling
0 likes · 27 min read

This article details the architecture, design principles, data preparation methods, verification processes, and error‑handling strategies of ZuanZuan's payment reconciliation system, highlighting how large‑scale data, binlog ingestion, Hive archiving, and MQ‑based workflows ensure accurate and secure financial settlements.
HiveMQbackend architecture
0 likes · 11 min read

The article explains that distributed transactions in micro‑service architectures are difficult because they must guarantee atomicity across heterogeneous services, handle time‑outs, and reconcile results using unique transaction IDs, undo‑logs, or NoSQL strategies, while balancing locking, availability, and consistency trade‑offs.
IdempotencyTransaction IDdistributed transactions
0 likes · 18 min read

This article details the background, architecture, data preparation methods, massive‑data handling strategies, verification processes, and error‑handling mechanisms of ZuanZuan's channel reconciliation system, highlighting design choices such as binlog ingestion, task‑driven bill downloads, sharding with Hive archiving, and MQ‑based reconciliation to ensure financial data consistency and safety.
HiveMQdata pipeline
0 likes · 11 min read

React 16 feels smoother than React 15 because its new Fiber architecture breaks state updates into small, priority‑aware units that the Scheduler runs asynchronously, allowing high‑priority user input to render first while lower‑priority work is paused and resumed, eliminating the lag seen in full‑tree re‑renders of React 15.
FiberFront-endReact
0 likes · 16 min read

This article provides an in‑depth analysis of the Strimzi Kafka Operator, covering its core features, multi‑layer architecture, detailed installation steps on Kubernetes, Kafka cluster creation, production/consumption workflows, and the internal reconciliation mechanisms that enable automated scaling, storage tuning, and fault‑recovery.
KafkaKubernetesOperator
0 likes · 11 min read

This article details the design, challenges, and monitoring strategies of Alibaba's travel billing system, explaining how a modular backend architecture, multi‑way reconciliation, full‑link monitoring, and a configurable expression engine enable near‑perfect bill accuracy and automated settlement for enterprise customers.
BackendBillingOperations
0 likes · 17 min read

This article describes how a payment reconciliation system progressed from a simple MySQL‑based solution through a Hive‑based big‑data approach to a high‑performance StarRocks architecture, detailing the integration of Flink, DataX, and SQL adaptations that dramatically improved query speed, cost, and operational efficiency.
ETLFlinkSQL
0 likes · 8 min read

This article presents a comprehensive design of a distributed reconciliation system that handles tens of millions of daily payment orders by using a six‑module architecture, Kafka for decoupled state transitions, Hive for large‑scale data processing, and Java‑based plug‑in patterns to achieve six‑nine accuracy and significant operational cost savings.
HiveJavaKafka
0 likes · 15 min read

This article outlines the critical business areas, core performance metrics, testing approaches, templates, and tools—including Hyperledger Caliper—required to effectively implement and evaluate blockchain reconciliation systems for secure, accurate, and scalable financial operations.
BlockchainHyperledger Caliperreconciliation
0 likes · 10 min read

This article explains the purpose, architecture, modules, and detailed design steps of a payment reconciliation system, covering internal and channel reconciliation, data acquisition, file parsing, storage, transaction matching, error handling, and settlement processes for robust backend payment operations.
Backendpaymentreconciliation
0 likes · 11 min read

This article explains the evolution of multiplayer game server architectures, compares client‑server and P2P models, details communication via long‑lived sockets, and explores frame‑sync, state‑sync, prediction, reconciliation and interpolation techniques with a complete React + Socket.io demo.
Socket.IOSynchronizationframe sync
0 likes · 18 min read

This article explains how a payment company's reconciliation center matches internal transaction records with bank clearing data, detailing the clearing reconciliation system, reconciliation definitions, data sources, processing logic for one‑to‑one, many‑to‑many, and one‑to‑many scenarios, as well as module functions, exception handling, and data recovery procedures.
Operationsaccountingclearing
0 likes · 28 min read

This document provides a comprehensive overview of the settlement reconciliation system used by payment companies, detailing fund inflow and outflow matching with banks, the role of the reconciliation center, various reconciliation methods, functional modules, and procedures for handling exceptional data recovery.
accountingbank integrationfinancial operations
0 likes · 27 min read

This article explains the design of a high‑throughput payment reconciliation system that handles daily transaction volumes in the tens of millions, covering architecture, data collection, big‑data processing with Hive and Spark, handling of suspicious records, and integration with a data platform.
paymentreconciliationsystem design
0 likes · 30 min read

The article provides a comprehensive overview of payment‑system clearing and reconciliation, detailing fund inflow/outflow matching, reconciliation center functions, various one‑to‑one, many‑to‑many and one‑to‑many matching rules, data import, error handling, and auxiliary modules such as balance entry and abnormal data recovery.
FinancialOperationsSystem
0 likes · 29 min read

This article outlines the purpose, methods, common scenarios, user groups, and a five‑step workflow—including data preparation, cleaning, verification, discrepancy handling, and result reporting—for designing an effective financial reconciliation system.
Product Designdata preparationdiscrepancy handling
0 likes · 10 min read

React Fiber replaces the old Stack Reconciler with a linked‑list of Fiber nodes that enable incremental, pause‑and‑resume rendering, priority scheduling, and a three‑step commit phase, allowing smoother asynchronous updates, better performance, and the foundation for Concurrent Mode and Suspense.
Concurrent ModeFiberJavaScript
0 likes · 23 min read

This article introduces the concept, core capabilities, and architectural evolution of a reconciliation center—from its initial 1.0 design through 2.0 and 3.0 upgrades—highlighting problem statements, solution approaches, and the applicable scenarios that make it essential for large‑scale data consistency in modern micro‑service systems.
BackendOperationsarchitecture
0 likes · 14 min read

Alibaba migrated Xianyu Coin’s points from the legacy KingTower platform to the new Banliang service using a four‑phase, service‑based approach—preparation, active/passive data migration with distributed locks, dual‑write for consistency, reconciliation, and a gradual service switch—completing the transition in a month without user impact.
Backend EngineeringRedis LockService Integration
0 likes · 11 min read

This article explains how to implement payment‑code integration for major wallets like WeChat Pay and Alipay, covering synchronous API behavior, password‑prompt handling, revocation strategies, order status nuances, and daily reconciliation techniques to ensure accurate financial reporting.
AlipayPayment IntegrationRevocation
0 likes · 10 min read

This article, excerpted from the book "Software Architecture Design: Integrating Large‑Scale Website Technical and Business Architecture," systematically presents seven practical solutions—including two eventual‑consistency approaches, two compromise methods, TCC, state‑machine retry with idempotence, and reconciliation—to address the pervasive challenges of distributed transactions in micro‑service systems.
2PCTCCdistributed transactions
0 likes · 25 min read

This article provides a detailed overview of payment system architecture, covering functional modules, core payment, refund, reconciliation, and settlement workflows, as well as design considerations such as gateway integration, routing, risk assessment, asynchronous processing, and transaction logging for robust backend development.
Risk Assessmentgateway integrationpayment architecture
0 likes · 19 min read

This article explains why React Fiber was introduced, describes its core concepts such as the fiber tree, work‑in‑progress tree, double buffering, priority scheduling, and lifecycle changes, and summarizes the new capabilities it brings to improve UI performance and responsiveness.
FiberReactScheduling
0 likes · 10 min read

The article describes Meituan’s reconciliation system for delivery settlement, which ingests diverse external data, normalizes it, performs multi‑stage offline and online verification to detect missing, duplicate, or incorrect settlements, and automatically records and resolves errors through a unified balancing center, ensuring fund safety at tens‑million‑order scale.
BackendData Consistencyfinancial safety
0 likes · 18 min read

Meituan’s settlement and reconciliation platform was rebuilt from a single‑threaded, month‑end batch system into a distributed, multi‑threaded, real‑time service that abstracts core models, uses lock‑free processing, sharding, and dedicated Kafka topics, achieving millisecond latency for millions of daily bills across 17 business lines.
Backenddata-processingdistributed-systems
0 likes · 20 min read

The article explains how a payment center builds a SaaS‑style, multi‑entity, multi‑currency fund processing platform that handles accounting, day‑end, monitoring, reserve management, billing, and reconciliation, detailing business scenarios, fund flow models, system components, and methods to ensure data accuracy.
financial architecturefund processingmulti-currency
0 likes · 10 min read
