2 ms·
I feel like you're arguing with a straw-man here. I've not said that most sites should avoid relational databases. I've said that there exist applications whe
by wheels 18y ago
I feel like you're arguing with a straw-man here. I've not said that most sites should avoid relational databases. I've said that there exist applications where RDBMSes are less than ideal and graph / key-value systems seem to be a better fit. We seem to agree there. We can argue over how large that slice is, but since we'd both be making numbers up, it seems rather pointless.
Your business seems to be invested in pushing out commodity RDBMSes. Mine is focused on applications that need super fast graph traversal. It's no shocker that we have a different take on this. :-)
- justinsb 18y agoJust read your profile & followed the link to your company. I like the product you guys are building, and certainly understand where you're coming from now. I just take exception to the name-dropping of big-companies as examples of companies that have decided against relational databases, when they've only done so in incredibly narrow niches of very large systems. It would be more accurate to say they've decided against traditional filesystems, yet we don't see articles proclaiming the death of the filesystem. This is the real straw man argument, I'd suggest. I'm sure there are applications out there for whom graph databases are ideal; the only way to get real numbers is to try to bring a product to market, so I wish you well!