3 ms·
Over time I've come to take this a step further. I feel people reach for a graph database way too early. Most use cases that most people have will work fine in
by jghn 4y ago
Over time I've come to take this a step further. I feel people reach for a graph database way too early. Most use cases that most people have will work fine in a standard relational setup. And that brings with it the benefits of using technologies like Postgres that have stood the test of time. So I treat it as I do any performance consideration: first demonstrate that you actually need to go down the path less traveled, don't just assume you need to do so.
- rajman187 4y agoCompletely agree. In fact, even massive graph data can make use of a relational database + caching [1] [1] https://engineering.fb.com/2013/06/25/core-data/tao-the-power-of-the-graph/ https://engineering.fb.com/2013/06/25/core-data/tao-the-powe...