KDB/Q Architecture

In this section of the blog, our primary focus will be on the realm of KDB/Q Tick architecture. We will start with the plain vanilla tick setup, examining every single process in detail, describing the role of each indvidual process, their memory usage over the course of the day, explorer essential design considerations, and potential pitfalls to be mindful of. We will then move on to more advanced tick configurations, unveiling additional services you can build to enhance the foundational tick configuration.

📄️ The Plain Vanilla Tick Setup

A basic KDB/Q Tick setup consists of three essential elements such as a Tickerplant (TP), a Real-Time Database (RDB), and a Historical Database (HDB). Additionally, this configuration involves the integration of two external processes, namely a Data Feed and a Feed Handler. The provided image below serves as a visual representation of this architectural arrangement.

📄️ Advanced KDB/Q Architecture

In a previous blog post, we covered the Plain Vanilla Tick Setup, a foundational KDB/Q framework that serves as the starting point for more advanced systems. In this post, we’ll explore a more sophisticated architecture and walk through the key design decisions you can make when building a complete KDB/Q stack.