Why use Kx instead of traditional databases?
Kx has become the major player in our target market of high-performance, high-volume databases. Kx is used instead of traditional databases because of its performance and flexibility. In recent years, traditional databases have struggled to cope with massive increases in data volumes, and the old model of overnight reporting is no longer acceptable in real-time business. The business intelligence/OLAP/data warehousing structures that were built to make relational databases more efficient are also under increasing pressure to deliver faster analysis — and they cannot. Some in-memory databases and real-time data products deliver speed as long as the data is in memory, but they solve only a small part of the data volume and data analysis problem. The limitations of traditional databases pushed many companies to write custom built applications, typically storing data in flat files. These can work fine for simple queries hand- coded in C, but typically cannot support ad hoc queries, or the
