Live data from Hacker News

Getting Started with Graph Databases

academy.datastax.com

11–20 of 35 posts

Re: Getting Started with Graph Databases

#11
I was very interested in the subject, but hated this video.

Very superficial, started off with a complicated relational schema to criticize relational databases, but never ended up explaining how a graph database would simplify the problem. I thought that the graph database concepts + language was way more complex than SQL schema + language.

Very fast talking and moving of slides, is this supposed to sound or look smart? On top of that, 50% of the time the video was a close up to the presenter's face moving left and right in an awkward fashion.

Re: Getting Started with Graph Databases

#13
Is Titan going to survive even though datastax bought out the team? Their github repo hasn't been very active recently.

My issue with graph dbs is that as requirements change you usually have to add more granularity to the edges and nodes. Eventually the schema becomes much more complicated than a RDB.

Re: Getting Started with Graph Databases

#14
post #6
post #4

FYI: There are two "Graph Databases 101" posts on the front page now. This one and the older one here: https://news.ycombinator.com/item?id=11257280 (4 hours ago, 15 comments)

It seems he did it to gain votes.

Except they're two different articles posted by two different people. This seems like an amusing coincidence.

Re: Getting Started with Graph Databases

#15
post #13

Is Titan going to survive even though datastax bought out the team? Their github repo hasn't been very active recently. My issue with graph dbs is that as requirements change you usually have to add more granularity to the edges and nodes. Eventually the schema becomes much more complicated than a RDB.

FWIW AWS recently added DynamoDB integration support for it.

https://aws.amazon.com/blogs/aws/new-store-and-process-graph...

Re: Getting Started with Graph Databases

#16
post #3

As I had zero experience with graph databases, this was generally a good intro, but the article could do with some polishing to save newbies like me from the underlying suspicion that they're missing something obvious. I tried just reading the tutorial without watching the video, and suffered some cognitive dissonance. At the end of the article, there's two diagrams that show the behaviour of jcvd.out() and jcvd.outE…

You're right, there's some inconsistencies in the code vs the slides. Must have missed that. I'll fix that going forward.

Re: Getting Started with Graph Databases

#18
post #11

I was very interested in the subject, but hated this video. Very superficial, started off with a complicated relational schema to criticize relational databases, but never ended up explaining how a graph database would simplify the problem. I thought that the graph database concepts + language was way more complex than SQL schema + language. Very fast talking and moving of slides, is this supposed to sound or look sm…

Good feedback. I might need similar feedback for my upcoming talk. I am about to give a talk about Cayley (open source graph db written in Go) and I am working on my slides http://oren.github.io/adventure-graphs

Let me know what you think and also join us on IRC (#cayley on freenode) if you find it interesting.

Re: Getting Started with Graph Databases

#19

This article overly inflates the complexity of graphs and databases in order to sound fancy. I've written a response that is very direct and shows how simple a graph database can be: https://github.com/amark/gun/wiki/Graph-Databases-101 .

Wow, you have some colossal nerve accusing others of trying to sound fancy.

Re: Getting Started with Graph Databases

#20

This article overly inflates the complexity of graphs and databases in order to sound fancy. I've written a response that is very direct and shows how simple a graph database can be: https://github.com/amark/gun/wiki/Graph-Databases-101 .

Hi. Presenter here. Honestly the goal wasn't to sound fancy. If you're going to work in the GraphDB world, you're going to come across this terminology.

If your concern around my intro is the complexity described of the relational world, well, that's kind of the point. Anyone with at least a few years experience in the RDBMS world has probably come across a project that's spiraled completely out of control with a outrageous number of many to many relationships that are almost impossible to work with. The role of the DBA just to manage your queries and tables is a reflection of that difficulty.

GUN looks like a cool project. Good intro, & thanks for the feedback.

Post reply on HN