kdb+ vs. Oracle TimesTen

kdb is well suited for real time tick data and time series analytics.

Incentivized

TimesTen is well suited for applications using smaller data or smaller data stores and where transaction response times are not as business critical. TimesTen is good for applications already accessing Oracle and need to cache data for quick read/write operations. TimesTen is not appropriate for large data dependent applications or applications requiring fast response times. In these cases, using Oracle database or Exadata is better

Incentivized

• Time series analysis. The built-in vector operations are extremely fast. Also with the q language you can code up any customized analytical ideas quickly.
• The database are all file based, very easy to maintain.
• Very solid and fast interface to websocket, so you can interface with javascript easily.

Incentivized

• With basic database experience, TimesTen has a very short learning curve.
• The installation and setup is easy and straightforward. The command line instructions are easy to follow.
• The error logging mechanism is simple and efficient. The system log files are helpful in troubleshooting problems with using TimesTen.
• The maintenance tools are user friendly and effective. Upgrading is easy and quick. TimesTen is almost a self-administrating database.

Incentivized

• Run time error message readability, particularly for new users.
• Backwards compatibility between versions.

Incentivized

• Provide better monitoring tools of TimesTen daemon, servers and connections.
• Improved support for APIs. The libraries lack the necessary code for applications to customize for applications using TimesTen.

Incentivized

switching costs

Incentivized

its ok

Incentivized

We don't use it.

Incentivized

Python is very commonly used for large data analysis and in general is much easier to pickup than kdb+. The biggest drawback of kdb+ is the learning curve.

Incentivized

Sybase does not have an in-memory database until version 15 so TimesTen was ideal for caching data. TimesTen has reliable replication and backing up mechanisms. Oracle takes longer to set up and use for most applications where as TimesTen is a smaller DBMS that is quick and easy to set up and use. TimesTen can connect to Oracle for caching data so using Oracle as a backend makes sense

Incentivized

• It perfectly solves most of our real time tick data needs.
• Finding good kdb resources is slightly difficult. Also new people trying to learn kdb experience a relatively longer learning curve.

Incentivized

• TimesTen has had a positive impact from a developer's perspective because implementing TimesTen is quick and easy. The benefits of TimesTen can be seen almost instantly. For instance, the application start up time is faster, the data is easy to maintain and the performance is fast for TimesTen clients.
• TimesTen has had a positive impact for the business because it can be made accessible to users via a GUI. This gives users transparency to the data at any time.
• The negative impact is that once the TimesTen database has grown too large, the application should move to using Oracle database or else it suffers from performance degradation and stability issues.

Incentivized