What is meant by a single architecture?
Most data management/data analysis solutions divide the world into real-time data and historical data. This makes it easier for partial approaches to claim proficiency at one or the other, but there are several disadvantages to the division, such as: • delays while real-time data is converted and written to the historical database • more complex queries to address both types of data • the cost in time and memory of marshaling from one format to another when passing data from one vendor application to another • similar but different sql dialects, each of which has to be tuned, optimised and debugged In contrast, kdb+ has one architecture for both, minimizing latency and simplifying queries.
