3 ms·
> That's not simple, that's a big change which requires a bunch of work. I feel like many of these criticisms of RDBMS come from a perspective of not working w
by simonw 7y ago
> That's not simple, that's a big change which requires a bunch of work.
I feel like many of these criticisms of RDBMS come from a perspective of not working with a great database migrations system.
I've made changes like this (one-to-many switched for many-to-many) using Django migrations many times over, and I find it easy. But that's because I've built up the experience with the tooling over time.
Learning migration tooling in this way feels like a much smaller lift to me than entirely switching to a graph database.
(I'm a big fan of Dgraph, but I've not yet found the right project to apply it. I'm not interested in it as a replacement for RDBMS, I want to use it to solve graph problems that are genuinely painful with a relational database. Easier schema changes aren't that for me.)
- mrjn 7y agoHey Simon, Totally see your perspective. You're already familiar with data migration, but not familiar with graph DBs. The former is just easier to do than to invest in the learning curve involved with the latter. Valid point. My take is more root-cause and principle based. If we were to think of a different way to build a DB, then avoiding a data migration altogether is a better approach. Avoiding the downtime, extra work, extra code and so on is just better for the user. Moreover, simpler data models, avoiding data duplication and such become very convincing features. It's also not so interesting to me when graph DBs are only applied to specific graph problems, like Page Rank and such. We didn't build Dgraph just to solve Page Rank. The reason we built Dgraph was because we saw the complex data modeling problem Google Knowledge Graph threw at us. Graph system allowed that problem to be solved in a really clean and simple way. And it's the same problem we see other companies dealing with as well.