4 ms·
Obviously, it also depends on exactly what kind of application you are building. If you primarily want to persist objects and indices that don't have good or e
by joe_the_user 15y ago
Obviously, it also depends on exactly what kind of application you are building.
If you primarily want to persist objects and indices that don't have good or easy analogue in the SQL world, a NoSQL solution is good solution because you don't have to bother with the unneeded SQL overhead.
If you've doing something that maps reasonably well into the relational model, well, that's what you should use. Rational technology has been around a long time and has been scaled to huge levels. And it seems fairly clear a social network maps pretty well to a relational model.