understanding tools for analyzing data
This is a guest post by Mark Street. If you like it be sure to check out his other posts, or find him on LinkedIn. If you are interested in being a guest blogger on enlist[q], please contact me. As we previously learnt, q/kdb+ has a callback function .z.ts which fires an event every x milliseconds, where x is the precision applied to the …
Continue reading “Extending .z.ts to execute multiple functions at different intervals”
q/kdb+ has several pre-defined functions in the dot z namespace such as .z.a to get the IP address, .z.h to get the host, and .z.b to get the dependencies. Today, we will discuss a callback function in the dot z namespace called .z.ts. .z.ts is a very simple timer function that is invoked at regular …
Things used to be much simpler just a few years ago when you had all your applications deployed in your on-prem datacenter. Sure, you had to manage all that yourself, but it was easy to deploy your applications on your finite number of servers. Things are much different now. Cloud computing has really taken off …
Continue reading “Enabling a modern hybrid cloud kdb+ stack with PubSub+”
Note: You can now subscribe to my blog updates here to receive latest updates. This post is the second post in a series of posts I have written as part of a data analytics pipeline spanning multiple languages, databases, and environments. You can find more about the pipeline in my final post here. A typical kdb+ architecture …
Continue reading “Publishing and Consuming messages from PubSub+ in a q/kdb+ stats process”
Note: You can now subscribe to my blog updates here to receive latest updates. A typical kdb+ architecture (in a market data environment) is composed of multiple q processes sharing data with each other. These processes usually are: feed handlers, ticker plants, real-time subscribers (rdbs, pdbs, bars etc), historical databases (hdbs) and gateways. Here is what the …
Continue reading “Bringing the power of pub/sub messaging to kdb+”