Why kdb+ and not another database? Language? - Kdb+ / qStudio

Home Forums Kdb+ / qStudio Why kdb+ and not another database? Language?

This topic contains 0 replies, has 1 voice, and was last updated by  admin 3 years, 6 months ago.

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #111147

    admin
    Keymaster

    I often get asked why is kdb+ used by banks why not XXXX?
    Where XXX is hadoop, mongodb,spark…..

    I would turn this around and ask what is your particular goal?
    – Take the essential use cases you need
    – What criteria does that give us for evaluating a technology stack
    – Let’s take into account the skill set of our team
    – And the projected Total Cost of Ownership

    Then under that criteria let’s see what is the best solution.

    We’ve previously posted a comparison of different column oriented databases.
    http://www.timestored.com/time-series-data/column-oriented-databases
    Nowadays I would expand this further to include data stores available in a particular language, data frames in R, pandas in python…

    For kdb+ list it’s strengths:
    http://www.timestored.com/kdb-guides/kdb-database-intro

    1. Kdb+ the Database – Column Oriented DB allowing fast timeseries analysis
    2. q language – fast, interpreted vector based language
    3. Combined power of kdb+/q – Change how you think!

    Now weight up the pros and cons and decide.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.