[johnisgood]

> My understanding was always that for relational data (e.g., social networks) you should use a relational database.

I thought you were supposed to use a graph database for that, like dgraph. Do I remember incorrectly?

> Dgraph is a horizontally scalable and distributed GraphQL database with a graph backend.

---

Edit: found the source... According to https://www.infoworld.com/article/3251829/why-you-should-use...:

"However, as with any popular technology, there can be a tendency to apply graph databases to every problem. It’s important to make sure that you have a use case that is a good fit. For example, graphs are often applied to problem domains like:

- Social networks

- Recommendation and personalization

- Customer 360, including entity resolution (correlating user data from multiple sources)

- Fraud detection

- Asset management"

[drstewart]

This is what I thought the tweet would be referencing, but since the author is talking about posts, comments, etc. the alternative is clearly not saying a graph database (which is good for social connections) is optimal.

Realistically, it just seems like a low-effort attempt to dunk on Parler for likes and retweets.