3 ms·
This reads like marketing material for your product rather than an unbiased comparison. Being in memory vs Neo4j doesn’t even seem like a fair comparison. I wo
by jsumrall 4y ago
This reads like marketing material for your product rather than an unbiased comparison.
Being in memory vs Neo4j doesn’t even seem like a fair comparison. I would hope to god your product is faster for that reason. But it’s like comparing a minivan vs an electric smart car. One is quick and fast but it has its limitations, and the other option is more versatile.
Also I think you’re limiting yourself if the positioning of your product is purely as a counter part to Neo4j, and riding on their coattails.
Glad to see some thoughts about benchmarking, but every vendor makes such a thing and, surprise surprise, they’re always better than the rest.
- mapleeman 4y agoWe plan to add more graph database vendors to this benchmark, this will not be just Memgraph vs Neo4j comparison, hence the name "bench graph". You are 100% right about comparing architecturally different database systems, it is hard to compare them, but they serve the same/similar purposes, we are mentioning that part in limitations methodology: https://github.com/memgraph/memgraph/tree/master/tests/mgbench#limitations https://github.com/memgraph/memgraph/tree/master/tests/mgben... We first added Neo4j since we are both compatible.