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.
Supply chain and platform breaches are no longer hypothetical. How fast can you patch your whole dependency tree, rotate every credential, and contain the damage? The best time to invest was before yesterday.
DHH is right that hand-writing code is no longer economically viable for most programmers. But the code was never the point, and the practice of software engineering is as valuable as it has ever been.
More people get to build software than ever, but the attention now required for security and breach recovery is draining a lot of the joy, especially for teams with legacy systems to bring up to date.
Get More Like This
Follow along as I build and share what I learn
Found this helpful? Share it with your network!