You Probably Don't Need a Graph Database
Just because the data is a graph, doesn't mean you need a graph database - especially if you're a small team
Just because the data is a graph, doesn't mean you need a graph database. Especially if you're a small team.
Situations I've been in where someone has proposed using a graph database: many
Number of those situations where a graph database was actually needed: 0
Situations I've been in where managing a graph database would have made everyone on and around the team's day to day life worse: all of them
Are graph databases useful? Yes, at a certain level of scale.
Do I want to be responsible for maintaining a system with one? Absolutely not.
Beware unnecessary complexity.
Related insights
You're Going to Need to Ship a Fix in Minutes, Not Days
Agents are making it cheap for attackers to find unlocked doors. The window to invest in CI, test coverage, and fast safe rollback is now.
GitHub Is on the Struggle Bus Again
GitHub is absorbing a tsunami of AI generated code, and the outages keep coming. I've never been more open to an agent native alternative.
Let Your Agents Review, But Look Before Humans Do
Agents can run multiple rounds of review and verification before you look. But ship to humans without looking yourself, and something subtle always feels off — because fully specifying a system that feels right to a human is hard.
Get More Like This
Follow along as I build and share what I learn
Found this helpful? Share it with your network!