Neo4j's 'property sharding' promises to overcome scalability struggle

Neo4j has introduced "property sharding" which, according to one analyst, will help overcome its earlier struggles with scalability, while also allowing transactional workloads on the same system. Illustration of some Gnu / wildebeest against orage VT100 terminals logged into Unix like systems Free Software Foundation rides …

[Anonymous Coward]

"property sharding"

I first read that as 'sharting'...

Which is no surprise as MS is involved...

[Anonymous Coward]

They certainly need to do something, Neo4j performance and scalability is currently shockingly poor.

[Anonymous Coward]

Words Have Meanings

Either no one bothered to look up "sharding" in a vernacular dictionary or someone thought that the word's connotations with methamphetamine and scatological processes were Just Right.

[Anonymous Coward]

I doubt this fixes other scaling issues …

Neo4j is notoriously resource-hungry, and performance often degrades quickly unless you layer on heavy indexing and allocate substantial memory. This update doesn’t appear to address those fundamental constraints, it looks more like they’ve finally added proper sharding into enterprise clustering, a capability that arguably should have been part of their clustering architecture from the outset.

Too bad you have to have an enterprise license to see if this is anything more than hype…