<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Xinchuang on vtoollab</title><link>https://vtoollab.com/tags/xinchuang/</link><description>Recent content in Xinchuang on vtoollab</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>admin@vtoollab.com (vtoollab)</managingEditor><webMaster>admin@vtoollab.com (vtoollab)</webMaster><copyright>© 2026 vtoollab</copyright><lastBuildDate>Mon, 24 Aug 2026 22:00:00 +0800</lastBuildDate><atom:link href="https://vtoollab.com/tags/xinchuang/index.xml" rel="self" type="application/rss+xml"/><item><title>Apex HyperDB vs Kingstar KMDB vs Hundsun LightDB vs HuaRui ATP T7: The Four Routes of Proprietary In-Memory Databases in Securities Brokerages</title><link>https://vtoollab.com/posts/apex-hyperdb-vs-kingstar-kmdb-vs-hundsun-lightdb-vs-huarui-atp-t7/</link><pubDate>Mon, 24 Aug 2026 22:00:00 +0800</pubDate><author>admin@vtoollab.com (vtoollab)</author><guid>https://vtoollab.com/posts/apex-hyperdb-vs-kingstar-kmdb-vs-hundsun-lightdb-vs-huarui-atp-t7/</guid><description>Apex&amp;rsquo;s &amp;lsquo;Full In-Memory + External Persistence&amp;rsquo;, Kingstar&amp;rsquo;s &amp;lsquo;Industry-Tailored within Low-Latency Platform&amp;rsquo;, Hundsun&amp;rsquo;s &amp;lsquo;HTAP Converged with Embedded In-Memory Engine&amp;rsquo;, and HuaRui&amp;rsquo;s &amp;lsquo;Message-Driven + In-Memory Computing&amp;rsquo;. Four distinct routes converge on microsecond latency and autonomous controllability.</description></item><item><title>The Past and Present of the Centralized Counter: Three Generations of Evolution in China's Securities Core Trading Systems</title><link>https://vtoollab.com/posts/the-past-and-present-of-the-centralized-counter/</link><pubDate>Mon, 24 Aug 2026 12:00:00 +0800</pubDate><author>admin@vtoollab.com (vtoollab)</author><guid>https://vtoollab.com/posts/the-past-and-present-of-the-centralized-counter/</guid><description>The Grand Centralized Counter used the Oracle RAC architecture to consolidate client, fund, and holding data from branches nationwide to headquarters, eliminating the &amp;lsquo;client locked in a single branch&amp;rsquo; model and laying the foundation for over a decade of securities trading. However, its deep reliance on the &amp;lsquo;IOE&amp;rsquo; architecture foreshadowed the Xinchuang substitution wave after 2020.</description></item><item><title>From HyperDB to LightDB: The Four Routes of Proprietary In-Memory Databases in Securities Core Trading Systems</title><link>https://vtoollab.com/posts/from-hyperdb-to-lightdb/</link><pubDate>Sun, 23 Aug 2026 20:00:00 +0800</pubDate><author>admin@vtoollab.com (vtoollab)</author><guid>https://vtoollab.com/posts/from-hyperdb-to-lightdb/</guid><description>The four proprietary in-memory database routes are not merely about technical superiority, but represent different vendors&amp;rsquo; answers to the fundamental question: &amp;lsquo;What data architecture should the core trading system use?&amp;rsquo; Understanding these four routes means understanding all the technical options for the Xinchuang substitution in the next five years.</description></item><item><title>From Oracle to OceanBase: The Practical Migration Path for Xinchuang in Fund Valuation and Accounting Systems</title><link>https://vtoollab.com/posts/oceanbase-vs-kingbasees/</link><pubDate>Sun, 23 Aug 2026 16:00:00 +0800</pubDate><author>admin@vtoollab.com (vtoollab)</author><guid>https://vtoollab.com/posts/oceanbase-vs-kingbasees/</guid><description>Ping An Fund&amp;rsquo;s valuation system completes EOD valuation for 96% of products before 19:00; Harvest Fund&amp;rsquo;s TA system smoothly migrates 70TB of data and 230+ stored procedures. These two benchmark cases outline a five-stage practical path: &amp;lsquo;Assessment → Dual-track → Migration → Tuning → Single-track&amp;rsquo;.</description></item><item><title>What's the Difference Between Apex A5's HyperDB and Kingstar's KMDB? Two Philosophies of In-Memory Databases</title><link>https://vtoollab.com/posts/from-hyperdb-to-kmdb/</link><pubDate>Sun, 23 Aug 2026 16:00:00 +0800</pubDate><author>admin@vtoollab.com (vtoollab)</author><guid>https://vtoollab.com/posts/from-hyperdb-to-kmdb/</guid><description>HyperDB is the core database base for Apex A5&amp;rsquo;s &amp;lsquo;compute-storage separation and De-Oracle&amp;rsquo; route, aiming to completely replace Oracle; KMDB is the storage component of Kingstar&amp;rsquo;s KOCA-LDP low-latency platform. The two differ fundamentally in positioning and architectural roles.</description></item><item><title>From FS2.5 to UF3.0: The Duel of the Two Titans in Securities Core Trading Systems' Xinchuang Initiative</title><link>https://vtoollab.com/posts/from-fs20-to-uf30/</link><pubDate>Sun, 23 Aug 2026 10:00:00 +0800</pubDate><author>admin@vtoollab.com (vtoollab)</author><guid>https://vtoollab.com/posts/from-fs20-to-uf30/</guid><description>Kingstar&amp;rsquo;s FS2.5 and Hundsun&amp;rsquo;s UF3.0 represent two distinct paths for the Xinchuang initiative in core securities systems: Native Reconstruction vs. Legacy Evolution. How will the two titans attack and defend before the 2027 deadline?</description></item><item><title>From KCBP to KOCA-LDP: The 30-Year Evolution of Kingdom Technology's Middleware</title><link>https://vtoollab.com/posts/from-kcbp-to-koca/</link><pubDate>Sun, 23 Aug 2026 10:00:00 +0800</pubDate><author>admin@vtoollab.com (vtoollab)</author><guid>https://vtoollab.com/posts/from-kcbp-to-koca/</guid><description>&lt;p&gt;📌 &lt;strong&gt;Core Argument&lt;/strong&gt;: The evolution of Kingdom Technology&amp;rsquo;s middleware is essentially an industrial history of China&amp;rsquo;s securities trading systems transitioning from &amp;ldquo;branch-level&amp;rdquo; to &amp;ldquo;enterprise-level&amp;rdquo;, from &amp;ldquo;centralized trading&amp;rdquo; to &amp;ldquo;distributed low-latency ultra-fast trading&amp;rdquo;, and from &amp;ldquo;IOE dependency&amp;rdquo; to &amp;ldquo;full-stack IT Application Innovation (Xinchuang)&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;This main thread can be clearly divided into five stages: the introduction of self-developed middleware into securities trading systems around 1998 → KCBP/KCXP becoming the cornerstone of domestic financial middleware in 2003 → the initiation of the 5th-generation core trading and settlement technology platform in 2017 → the release of the KOCA cloud-native platform in 2019 → and the iteration of the KOCA-LDP distributed low-latency platform to V2.0 in 2023.&lt;/p&gt;
&lt;p&gt;Every leap in each stage was not an isolated technical upgrade, but the result of the combined effects of brokers&amp;rsquo; business demands, regulatory environments, hardware computing power, and the Xinchuang (IT Application Innovation) strategy. Understanding this evolutionary path means understanding the complete trajectory of China&amp;rsquo;s FinTech self-reliance and controllability over the past 30 years.&lt;/p&gt;</description></item><item><title>Hundsun UF3.0 vs Kingstar FS2.5 vs Apex A5 vs HuaRui ATP T7: A Panoramic Comparison of the Four Titans' Technical Routes in Securities Core Trading Systems</title><link>https://vtoollab.com/posts/broker_core_trading_system_comparison/</link><pubDate>Sun, 23 Aug 2026 01:00:00 +0800</pubDate><author>admin@vtoollab.com (vtoollab)</author><guid>https://vtoollab.com/posts/broker_core_trading_system_comparison/</guid><description>The essence of the four-titan duel is not about technical superiority, but a direct collision of four engineering philosophies — legacy evolution, native reconstruction, De-Oracle substitution, and ultra-fast specialization — ahead of the 2027 Xinchuang deadline.</description></item></channel></rss>