Likelihood to Recommend Neo4J is great for creating network graphs or illustrating how things are related. It is also good for finding individuals or things that have greater influence than others in a system. It is not appropriate if you have standard data sets that can be analyzed using conventional methods or visualized using
Tableau , for example.
Read full review 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
Read full review Pros Mature Query language, I found Cypher QL to be mature in handling all sorts of problems we throw at it. Its expressive enough to be intuitive while providing rich features for various scenarios. Native support for REST API, that makes interacting with Neo4J intuitive and easy. Support for Procedures in Java, procedures are custom code that could be added to the Neo4J to write custom querying of data. The best part about the procedures is it could be invoked using the REST API. This allows us to overcome any shortcomings from their Cypher query language. Nice UI and interface for executing the Query and visualizing the response. UI access controlled by User credentials allows for neat access controls. Awesome free community edition for small-scale projects. Read full review 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. Read full review Cons One of the hardest challenges that Neo4j had to solve was the horizontal scaling problem. I am not updated on recent developments, but at the time of my use, I couldn't find a viable solution. Neo4j does not play with other open source APIs like Blueprint. You have to use the native Neo4j API. There wasn't a visual tool to see your data. Of course, third party tools are always available, but I would have loved something which came with the Neo4j bundle. I love that Docker comes bundled with Kitematic, so it's not wrong to hope that Neo4j could also ship with some default visualization software. Read full review 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. Read full review Usability [Based on] Query Language, Performance on small and large data sets, integration and deployment, analysis, API support, Interactive UI.
Read full review Alternatives Considered Neo4j is a graph store and has different use cases compared to another NoSQL Document store like
MongoDB .
MongoDB is a bad choice when joins are common as existing operators for joining two documents (similar to tables in a relational store) as Mongo 3.5 use SQL like join algorithms which are expensive.
MongoDB is a great choice when distributed schemaless rich document structures are important requirements. Cross document transaction support is not native to
MongoDB yet, whereas Neo4J is ACID complaint with all its operations.
Read full review 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
Read full review Return on Investment Positive: Less complex queries on graph structures, than in relational databases. Negative: maintenance is a huge deal, things doesn't work and break, requiring lengthy restore operations. Read full review 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. Read full review ScreenShots