5 ms·

Memgraph is laughably expensive - I honestly wonder what anyone actually uses it for outside of companies that just don't care about infra spend.

mbuda 1y ago
DISCLAIMER: The co-founder and CTO of Memgraph here. To add more context, Memgraph Enterprise pricing is explained under https://memgraph.com/pricing https://memgraph.com/pricing: "Starting at $25,000 per year for 16 GB, Memgraph has an all-inclusive, simple pricing model that scales with your workload without restrictions. No charge for compute. No charge for replicas. No charge for algorithms. No Surprises.". In addition, Memgraph Community is free (standard BSL license, which turns into Apache2 4 years after release date, https://github.com/memgraph/memgraph/blob/master/licenses/BSL.txt https://github.com/memgraph/memgraph/blob/master/licenses/BS...), and it has many features that are usually considered enterprise (users, replication, not a single degradation in performance or scale, etc.). Please elaborate more about why the pricing seems expensive, or put it into the infra-cost perspective :pray:
- smarx007 1y ago
  I think on this site anything that's more expensive than free is considered expensive. Countless arguments have been had on Oracle vs Postgres, including lock-in. I think lock-in is more important to consider than license cost. To be fair, it is quite nice for the pricing to be transparent. And I think it's somewhat competitive w.r.t. Stardog, for example. The community version is less restricted than Ontotext, for example.
  - kendallgclark 1y ago
    Not really competitive with Stardog given our leading LLM integration with Voicebox. 85% pass@1 to exit POV with new customer.
smarx007 1y ago
If you want a production-grade graph DBMS, you don't have that many OSS options that are reliable and well-supported. In the relational space, it took OSS options like Postgres many decades (and somehow paid-for person-years) to get to a place where enterprises seriously consider migrating off Oracle to it.
- jcgrillo 1y ago
  Are there any? My experience so far with graph databases is a resounding failure.
  - UltraSane 1y ago
    I'm using Neo4j to build a CMDB and it is awesome.
    - jcgrillo 1y ago
      That's good to hear, how large is the graph you're building (nodes, edges) and how do queries perform?
      - lolive 1y ago
        The big issue we have had with Neo4J was with replication, when we do MASSIVE updates. For the rest, it handles the charge reasonably well.
        jcgrillo 1y ago
        What constitutes a massive update?
      - UltraSane 1y ago
        Not very big since it is only used internally at my company. 5 digit node count and high 6 digit relationships count. Queries are usually very fast unless you try to do something stupid that ends up having to search the entire graph. indexing critical high-cardinality properties and thinking of relationships as a kind of index help a lot with query performance. I have been meaning to test how fast memgraph is.

mbuda 1y ago

DISCLAIMER: The co-founder and CTO of Memgraph here. To add more context, Memgraph Enterprise pricing is explained under https://memgraph.com/pricing https://memgraph.com/pricing: "Starting at $25,000 per year for 16 GB, Memgraph has an all-inclusive, simple pricing model that scales with your workload without restrictions. No charge for compute. No charge for replicas. No charge for algorithms. No Surprises.". In addition, Memgraph Community is free (standard BSL license, which turns into Apache2 4 years after release date, https://github.com/memgraph/memgraph/blob/master/licenses/BSL.txt https://github.com/memgraph/memgraph/blob/master/licenses/BS...), and it has many features that are usually considered enterprise (users, replication, not a single degradation in performance or scale, etc.). Please elaborate more about why the pricing seems expensive, or put it into the infra-cost perspective :pray:

smarx007 1y ago
I think on this site anything that's more expensive than free is considered expensive. Countless arguments have been had on Oracle vs Postgres, including lock-in. I think lock-in is more important to consider than license cost. To be fair, it is quite nice for the pricing to be transparent. And I think it's somewhat competitive w.r.t. Stardog, for example. The community version is less restricted than Ontotext, for example.
- kendallgclark 1y ago
  Not really competitive with Stardog given our leading LLM integration with Voicebox. 85% pass@1 to exit POV with new customer.

smarx007 1y ago

If you want a production-grade graph DBMS, you don't have that many OSS options that are reliable and well-supported. In the relational space, it took OSS options like Postgres many decades (and somehow paid-for person-years) to get to a place where enterprises seriously consider migrating off Oracle to it.

jcgrillo 1y ago
Are there any? My experience so far with graph databases is a resounding failure.
- UltraSane 1y ago
  I'm using Neo4j to build a CMDB and it is awesome.
  - jcgrillo 1y ago
    That's good to hear, how large is the graph you're building (nodes, edges) and how do queries perform?
    - lolive 1y ago
      The big issue we have had with Neo4J was with replication, when we do MASSIVE updates. For the rest, it handles the charge reasonably well.
      - jcgrillo 1y ago
        What constitutes a massive update?
    - UltraSane 1y ago
      Not very big since it is only used internally at my company. 5 digit node count and high 6 digit relationships count. Queries are usually very fast unless you try to do something stupid that ends up having to search the entire graph. indexing critical high-cardinality properties and thinking of relationships as a kind of index help a lot with query performance. I have been meaning to test how fast memgraph is.