Hacker News Reader

Comment by jaxk | Hacker News Reader

yeah, I see these examples a lot so safe to say its niche and used by large banks, feds etc and not everyday businesses?

View on HN

No, because although individually each use case above could be described as niche (maybe) - there’s so many different ones, in so many different industries, there’s clearly a general use case.

I’ve been a developer with 18 years commercial experience now and I’ve seen graph databases in all size businesses as I’ve travelled the world, from 1-2 person startups to huge online casinos, heck, I’m a single person startup and I have two myself, one with 200,000,000 nodes and there’s no way a traditional database could do what that system is doing (I tried with Postgres, HBase on Hadoop, and Cassandra)

Sure they are not as common as traditional DBs, but they are far from niche, that’s why (as you said in your original post) there’s so many products in this space competing - they are actually a thing, they are actually useful, and for some projects, critical.

yeah but as a novice dev I have never come across a job listing that needed a graph db expertise of any kind, there are tons that need nosql though, along with traditional rdbms of course, why is that?

Actually upwork seeems to have plenty, and unless I'm mistaken they are all of "(re)write cypher query" kind.

What is your graph db of choice? What are the more popular ones in your opinion?

What do you mean with "everyday businesses"? I would not say that graph databases are niche...

I wouldn't say they are niche, but many people I work with would model these systems in relational or no sql databases rather than pick a graph database for such a specific use case. With the popularity of microservice approach, this may be changing. Traditionally applications were based around 1 or few single datastores.

exactly, seems graph db just help reduce verbosity of sql query if cypher or something else is used.

Reply on news.ycombinator.com