<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>HyperDB on vtoollab</title><link>https://vtoollab.com/tags/hyperdb/</link><description>Recent content in HyperDB 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/hyperdb/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>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>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></channel></rss>