Graph DBs vs. Relational DBs (1 Viewer)


Local time
Today, 13:14
Apr 14, 2020
past few days i've been reading up on graph DBs in my spare time and i found it quite exciting.
Has anyone here had any experience with those in a business enviornment?
Also, anybody knows of any examples where a company would use a graph db for their day to day work switching from a relational db?


Registered User.
Local time
Today, 07:14
Mar 5, 2004
Funny you should be posting about this today. I don't happen to have any experience with the topic but just yesterday I came across this information and it intrigued me:

If you haven't seen it then maybe it will be helpful.



Super Moderator
Staff member
Local time
Today, 12:14
Feb 19, 2013
I don't know much about it - however the company my wife works for is using a graph database as a people network system. However from what I have seen it still relies heavily on good relational management and table design (plus good data). Perhaps unlike RDBMSs it forces a user to to adopt good practice? The link provided by shadow has a comparison of a complex sql query of 100's of lines v the equivalent 5 or 6 lines in Cipher (the equivalent of SQL). What it doesn't show is what the underlying data looks like. For example the complex sql uses union queries which is typically an indicator of poor design. With good design, the sql statement could be just as short.

That said, graph enables you to add properties to relationships - the sql equivalent would be a separate many to many join table. So may well have a faster operating efficiency as it is intended to handle billions of bits of data. It also claims to be more agile - easy to add in new properties for example. Well, it's easy to add a new field to a table, it's what you do with it once it is there that takes the time.

I suspect where it wins is where the style of the development brief is based on 'I know what I want and will recognise it when I see it' - which lets face it, with the current trend for short term investment is likely to be easier to build on as the world changes more and more rapidly.

In summary, looks like a) an enterprise scale system and b) still requires good relationship management but c) does this in a way that is perhaps a bit more intuitive.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

Top Bottom