Using the same logic, a key/value database is also a graph database?

Isn’t the biggest benefit of graph databases the indexing and additional query constructs they support, like shortest path finding and whatnot?

▲

sorokod 6 hours ago | parent | next [-]

Yes, the author is likely unaware of this. They see markdown files with links, so a graph and the set of those files, so a "database".

https://neo4j.com/docs/graph-data-science/current/algorithms...

▲

lamasery 5 hours ago | parent | next [-]

Neo4j looooooves the "if you think about it, everything is graphs!" marketing maneuver. They (their marketing department) were the very first thing I thought of when I read this headline.

▲

zadikian 4 hours ago | parent [-]

"Everything is graphs, so let's use a graph DBMS for anything" is a classic blunder

	▲	lamasery 2 hours ago \| parent [-]
		I've seen it work to sell their product to managers who definitely should have gone with something else, so I get why they do it. It works.

▲

esafak 6 hours ago | parent | prev [-]

His argument is that the LLM is the query engine. By that logic you can approximate anything since LLMs can.

	▲	sorokod 5 hours ago \| parent [-]
		Indeed, what is the point of links/edges when the llm can figure out the relations by itself?

▲

volemo 5 hours ago | parent | prev [-]

I think the confusion stems from the fact that we call a database what is really a database management system.

	▲	rzzzt an hour ago \| parent \| next [-]
		I'd just like to interject for a moment. What you're refering to as a database, is in fact a database management system, or as I've recently taken to calling it, database plus management system.
	▲	altmanaltman 4 hours ago \| parent \| prev [-]
		You confuse the raw fist with the master who calculates the shortest path to your destruction.