Likelihood to Recommend Less Appropriate Scenario: 1) Small Scale or Low Budget Projects 2) Organizations with limited expertise in cloud technologies may find the learning curve steep, especially if they are not familiar with the IBM Cloud platform 3) If database requirements are highly dynamic and change frequently, the comprehensive features and management provided by IBM Cloud Databases might be overkill. A more flexible, self-managed solution could be preferable for adapting to rapid changes.
Read full review 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 Pros The ease of setup was effortless. For anyone with development experience, a few simple questions such as name and login data will get you set up. The web application to manage cluster settings, billing settings and even introspect the data was simple and most importantly worked all the time. This can not always be said for web interfaces of other products. Read full review 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 Cons Better cost reports, before just increasing to another tier, thus increasing the price. This is critical for early stage startups, where budget is tight. Add more data center options. As a comparison, a similar service, Aiven.io has dozen more options than Compose (basically all big cloud providers). We moved from AWS to Digital Ocean, which made us stop using Compose, since Compose forces us to be either on IBM or AWS. Read full review 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 Likelihood to Renew IBM is our trusted partner which never failed to meet our expectations. Stability, efficiency, usability and security is a must have for our business which is fully provided by IBM Cloud Databases
Read full review Usability It is great the only things I have stumbled upon is the non standard port 80 they use and sometimes expired SSL certificate.
Read full review [Based on] Query Language, Performance on small and large data sets, integration and deployment, analysis, API support, Interactive UI.
Read full review Support Rating Support is helpful enough, but we haven't always had questions answered in a satisfactory manner. At one time we realized that Compose had stopped taking database snapshots on its two-per-day schedule, and had in fact not taken one for many days. Support recognized the problem and it was fixed, but the lack of proactive checks and the inability to share exactly what happened has caused us to look elsewhere for production work loads
Read full review Alternatives Considered The reason why I choose IBM Cloud Databases is that the IBM cloud toolset is already being used in other functions of the company and by using IBM Cloud Databases, the other cloud tools are better embedded and integrated. If the company is set to use amazon tools, I would go for rds.
Read full review 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 Return on Investment Prove use cases prior to administering entire platform, obtain ROI faster Able to achieve the technological components of our advanced analytics team without full scale purchase of AI platform Developed several studies to prove out cloud Db value, speed to deploy Read full review 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 ScreenShots