4 ms·
Looked into your product and saw this: https://memgraph.com/blog/neo4j-vs-memgraph https://memgraph.com/blog/neo4j-vs-memgraph > There is a broad number of dri
by alexchantavy 4y ago
Looked into your product and saw this: https://memgraph.com/blog/neo4j-vs-memgraph https://memgraph.com/blog/neo4j-vs-memgraph
> There is a broad number of drivers in many different programming languages available for both solutions. While Memgraph only maintains a few in-house drivers that it develops and supports (C, C++, Python, Rust), most Neo4j drivers can also be used with Memgraph. This is due to the fact that both solutions use the Bolt protocol, labeled property graph model and Cypher query language.
Can I really create a Neo4j driver object from the official Neo4j Python driver and point it at Memgraph and my app code will work as expected?
- mapleeman 4y agoYep, that is possible. Actually, one of the community members few days ago did this: https://gigi.nullneuron.net/gigilabs/using-the-neo4j-bolt-driver-for-python-with-memgraph/ https://gigi.nullneuron.net/gigilabs/using-the-neo4j-bolt-dr... You just need to tell driver, it is not Neo4j. If you want to continue using the Neo4j driver. We actually also have GQL Alchemy, which is ORM for Python. Take a look here: https://memgraph.com/gqlalchemy https://memgraph.com/gqlalchemy
- alexchantavy 4y agoThanks for the helpful links! The ORMs we’ve experimented with tend to be too opinionated in their structure or have leaky abstractions or don’t allow configuring important settings like connection timeouts or don’t handle things like batch writes or transaction control correctly. For my use case it’s much better to simply drop in a bolt driver and watch it go.