3 ms·
First of all, "expensive writes and cheap reads" is the common case. Second, nothing about graph databases implies expensive writes and cheap reads.
by staticassertion 5y ago
First of all, "expensive writes and cheap reads" is the common case. Second, nothing about graph databases implies expensive writes and cheap reads.
- AtNightWeCode 5y agoThis is the ONLY reason to use a graph databases.... Go a head and down vote instead of learn something. :)
- staticassertion 5y agoThat is not the only reason to use a graph database, and you're not exactly making a compelling argument, or a coherent one. I doubt I have much to learn from you on the subject.