As happens, each generation thinks that what they have developed will supersede what has happened in the past. This involves a failure to understand the lessons

As happens, each generation thinks that what they have developed will supersede what has happened in the past. This involves a failure to understand the lessons of the past. As far as database technologies are concerned, no one technological model will fill every area to the exclusion of all the others. Graph based databases are not an exception here. They are a rehash of network databases from the past. They have their uses, but it is not universal by any means. What too many people have failed to understand is that SQL databases are not relational databases (though you can build a relational database on a SQL DBMS). There are certain problem domains for which different underlying DBMS's are a far better fit. It depends very much on what you are trying to achieve. No one technology will "win" as there are always problems that are better solved using a different tool. There is an old saying that is oft forgotten and that is: If all you have is a hammer, everything looks like a nail. We are supposed to have a large number of tools in our toolbox to solve the various problems that come before us. Let's be Master Craftsmen and use the whole range of tools available to us. This is applicable in the choice of database technology as it is in the choice of language or the choice of programming style or any other tool choice we may use.