kdb+&#x2F;q&#x2F;k are used for IOT applications [1], not just fin tec. After all, it is all time series data.<p>The benchmarks given in a response above by srpeck [2], shows spark&#x2F;shark to be 230 times slower than a k4 query, and using 50GB or RAM vs. 0.2GB RAM for k4. If RiakTS is relying on spark&#x2F;shark as the in-memory database engine, it is already at a big disadvantage compared to k in terms of speed, and all the RAM that is going to be required on those distributed servers.<p>I will have to look at the DDL&#x2F;math functions available in RiakTS too, since that is how you get your work done regardless of speed of access.<p>[1]  <a href="http:&#x2F;&#x2F;www.kdnuggets.com&#x2F;2016&#x2F;04&#x2F;kxcon2016-kdb-conference-may-montauk-ny.html" rel="nofollow">http:&#x2F;&#x2F;www.kdnuggets.com&#x2F;2016&#x2F;04&#x2F;kxcon2016-kdb-conference-ma...</a><p>[2]  <a href="http:&#x2F;&#x2F;kparc.com&#x2F;q4&#x2F;readme.txt" rel="nofollow">http:&#x2F;&#x2F;kparc.com&#x2F;q4&#x2F;readme.txt</a>