Neo4j's entire pricing model, even in cloud, is built around the idea that you'll have one centralized very large graph.
Many companies, like the one I'm at, have the opposite use case -- many, geo-distributed, tiny graphs and multiple (read: 3-5) pre-prod environments. They simply don't have a pricing model that supports customers like us.
They wanted to charge us something like 10% of our ARR for something that was just a component of one microservice.
tiny compared to the scale they're looking to sell but not exactly small. Also network-isolated.
A graph db is the right tool for this use case. Just not really theirs, although it could if they could understand how to sell it to us at a fair price.
Many companies, like the one I'm at, have the opposite use case -- many, geo-distributed, tiny graphs and multiple (read: 3-5) pre-prod environments. They simply don't have a pricing model that supports customers like us.
They wanted to charge us something like 10% of our ARR for something that was just a component of one microservice.