What needs improvement with Neo4j AuraDB?

One small thing that could improve Neo4j AuraDB is that the limited size of the free tier is not necessarily a problem. It is somewhat slower than when you have your own Neo4j desktop application, but it is still quite performant. For me, the thing that was the most painful is the seven-day expiration where you need to reactivate or restart it. That was perhaps the only thing that I found frustrating. I cannot give a perfect score because of this inconvenience of the seven-day reset. I would also appreciate the ability to share credentials in a confidential way so we could share a session that would be convenient. Additionally, it would be nice to have better access to historical query Cypher statements that were tested or examples of Cypher, which I believe nowadays with AI would be absolutely doable. Providing the user with suggestions and explanations of what the Cypher would mean would be helpful. Neo4j AuraDB is a very good initiation or way for someone new to knowledge graphs to become familiarized with them, but it is a lot to take in, especially if you come from SQL where everybody says it is an easy transition, but in fact it is not exactly the same approach. It would be interesting to have some examples. I would also appreciate better explanations when errors occur or when syntax is wrong. It is typically quite generic in what is wrong about it. If there was a way to get more information, that would be helpful.

If I say so, how Neo4j AuraDB can be improved, at a very minute level, I can say that the graphs, if I want things to be in three dimensions. Currently we get them in two dimensions. When we scale this up, the maps become complicated, and in two dimensions things can be complex in visualization purposes. When we put in filters, the connections also vanish sometimes. The visualization side is something that could help. Additionally, if there is a voice search capability, which we can implement, that would add more functionality. With so much AI involved, AI could be helpful if we put in our data and enable it to give insights from the networks already developed in the graph. Some insights could be shown to our client, indicating that their data already contains meaningful insights, which could serve an analytical purpose. Voice search on the graph would be easily understandable and provide faster outputs to the customer.

Neo4j AuraDB is a very strong platform, but there are a few areas for improvement. The pricing model can be somewhat unpredictable as your database grows, since costs scale with node and relationship counts. More transparency or cost estimation tools would be helpful. Additionally, importing large datasets should be smoother; bulk data sometimes requires extra tuning or batching to avoid timeouts. The documentation is good overall, but it would benefit from including more real-world production examples and best practices for optimized Cypher queries and scaling patterns. Lastly, on the lower-tier plans, the cold start time can be frustrating during production, so improving the setup speed would enhance the developer experience. One improvement that would make daily work easier is having better monitoring and performance analytics directly in the Aura dashboard. Currently, we rely on external tools and custom scripting to track query performance and resource usage. Having native, real-time insights would help us quickly identify slow queries or inefficient patterns. Additionally, smoother integration with our CI/CD pipelines would be beneficial, such as an easy way to manage schema migrations or automatically seed data, which would make our development and testing process more efficient. These small enhancements could streamline our workflow.

Key areas for improvement include service governance and communication, especially around subscription transitions and deprecations. There should be clearer visibility and warnings for legacy subscription lifecycle changes. Safer and more flexible migration windows are needed when forced migration is required. Users also need explicit UI guidance for re-linking subscriptions or understanding when re-linking is not possible. From a user perspective, process reliability is as critical as technical features.

I would love to see a Retool type of interface builder with Neo4j AuraDB. In that interface builder, all I need is a component inside Retool that can display a Neo4j graph, because currently, I can connect to the graph using a GraphQL endpoint on the Neo4j hosted Aura server, but the problem is when I get it on the other side, I can't see it other than in a table, so I want to be able to see it in a graph.

There’s room for improvement in Neo4j AuraDB, especially on the developer side. The learning curve can be steep, and the interface for developing and pushing code can be unnecessarily complex. It might be beneficial to simplify this process to help developers ramp up more quickly. Working with graph databases like Neo4j can be more challenging than standard databases, particularly for juniors and those new to graph technology. Streamlining the development process could make it easier for new users to get up to speed. This would be particularly useful for teams with less experience in graph databases. If I could add a feature to Neo4j AuraDB, I’d focus on improving the Bloom interface. It’s excellent for visualizing smaller datasets, but navigating through it becomes challenging as the data grows—say, past 100,000nodes. The interface works well for beginners but doesn’t scale effectively for more advanced users of large datasets. I want a UI that bridges the gap between the easy-to-use Bloom interface and more complex, text-based tools. This would help manage larger datasets more efficiently and improve performance.

I've experienced it crashing a few times, so stability could be better. For things to improve, I think the GUI on the cloud needs improvement. If it's more intuitive, someone new to it can spend less time on tutorials and pick it up faster. The truth is, if your product is good, you spend less time on advertising. I take my inspiration from Telegram. Their product was so good they didn't need to spend much on advertising. It just grew on its own.