6 ms·
Knowing some of the FC people first hand, MongoDB did actually serve them fairly well for a substantial amount of time. Until they started hitting max limits,
by CptCodeMonkey 13y ago
Knowing some of the FC people first hand, MongoDB did actually serve them fairly well for a substantial amount of time. Until they started hitting max limits, it didn't really make sense to move to c.
Going straight to C or something like it would have been almost cargo-cultish ( eg If we build industrial strength, we will get industrial levels of traffic ).
- threeseed 13y agoExactly. Can you imagine all of the Java/C developers telling Ruby developers that they are idiots and don't know anything about programming ? Simply because they choose a technology that is designed for developer productivity at the expense of scalability. Because that what seems to happen for every database discussion.
- sosborn 13y ago>Can you imagine all of the Java/C developers telling Ruby developers that they are idiots and don't know anything about programming ? Unfortunately this seems to happen all the time.
- lucian1900 13y agoThe better comparison would be to PHP, and indeed, no one should ever use tools of quality as poor as PHP or MongoDB.
- pjmlp 13y agoNo, because Ruby also runs on the JVM/.NET and has native code compilers available.
- jbellis 13y agoIt sounds like you're assuming that productivity and power are opposites. Four years ago or even two, Cassandra was much harder to develop against than MongoDB, but that's not the case today.
- CptCodeMonkey 13y agoJust as a historical note, I meant to type C Star ( C\* ) but HN's formatting changed c\* into C. C\* is shorthand for Cassandra.