[HN Gopher] No-SQL databases are glorified caches
       ___________________________________________________________________
        
       No-SQL databases are glorified caches
        
       Author : hernantz
       Score  : 23 points
       Date   : 2021-04-26 14:39 UTC (8 hours ago)
        
 (HTM) web link (hernantz.github.io)
 (TXT) w3m dump (hernantz.github.io)
        
       | [deleted]
        
       | j16sdiz wrote:
       | I think the no-sql vs sql war have ended already. Most of us now
       | know what they can or cannot do.
       | 
       | Nothing new or interesting in this article.
        
         | FractalHQ wrote:
         | What about the guy that decided to learn about databases 5
         | minutes ago? He doesn't know what they can or cannot do.
        
         | hernantz wrote:
         | You would be suprised to find out that mongodb is still popular
         | for the wrong reasons
        
       | noofen wrote:
       | RAM is a cache for the disk. Disk is a cache for the network.
        
       | vaughan wrote:
       | It's surprising that graph dbs aren't more popular.
       | 
       | Just as document dbs can be derived/denormalized from SQL dbs,
       | relational dbs can be derived from a graph.
       | 
       | Conceptually, data is a graph.
       | 
       | I always find the decision between 1-M and M-M is so sticky with
       | RDBMS, and with a graph, it can be whatever you want it to be.
        
         | tluyben2 wrote:
         | I have used 'graph dbs' (or stuff bolted onto something else
         | exposing a graph and/or being called a graph-db), mostly
         | commercial ones, for the past 20+ years because I have the same
         | feeling as you have; every one of them was too slow (and not
         | scalable but we didn't even get to that point). From absolutely
         | unusable to useable as a toy; one of them was 50k$/server and
         | it was a toy. But that was a long time ago; things moved on and
         | I hear good things about Dgraph.
         | 
         | So I will try it again, see if it works this time around.
        
           | daemonk wrote:
           | The flexibility of a graphdb translates to flexibility in
           | writing your queries. And that's my main problem with
           | graphdb. Query optimizations can be difficult. It is very
           | easy to write a query that logically does what you want, but
           | takes hours to run. And if you take a bit of time thinking
           | about how the query runs, you can optimize to run in
           | milliseconds.
        
       ___________________________________________________________________
       (page generated 2021-04-26 23:02 UTC)