DISCLAIMER: The co-founder and CTO of Memgraph here.
To add more context, Memgraph Enterprise pricing is explained under 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/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:
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.
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.
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.
A Configuration Management Database (CMDB) is a centralized repository that stores information about Configuration Items (CIs), including their attributes and relationships. It's a key component of IT service management (ITSM), providing visibility into the components that make up IT services, like hardware, software, and documentation
It can be incredibly useful. One example is to have every every process linked to the VM it is running on and the host the VM is running on and the TCP port the process is listening on. If you have all the correct relationships defined then you can write a query like this to find every process on every VM listening on port 80 on a given VM host.
MATCH p = (host:VMHOST {name: 'your_host_name'})-[:RUNS]->(vm)-[:HAS_SERVICE]->(service)-[:EXPOSES_PORT]->(port:TCPPORT {port: 80})
RETURN p
This can save a absurd amount of time for analyzing the impacts of failures and security isolation compliance.
