kdb+ vs. Oracle TimesTen

When you are dealing with large scale time series data, [there are] no better alternatives. I've seen some firms use other so called "big data" alternatives, and claim they can store the data just as efficiently. However, once you want to generate sophisticated analytics from the data, nothing beats kdb+

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

• Efficient computing.
• Code interpretation is fast.
• Designed with finance in mind.

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

• It is sometimes painful to accept the fact that KDB+ is not fully multithreaded.
• The ability to write shorter code for a complex logic is really good. But it makes it really cryptic. Cryptic codes are very difficult to maintain and extend.
• For some small institutions license cost is little high.

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

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

• Ability to get insights into a large production system.
• Ability to handle data volumes greater than more basic databases / query languages.

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