<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AMI on vtoollab</title><link>https://vtoollab.com/tags/ami/</link><description>Recent content in AMI 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>Sun, 23 Aug 2026 20:00:00 +0800</lastBuildDate><atom:link href="https://vtoollab.com/tags/ami/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>