happily, this is not a synchronous application with tens of thousands of concurrent users, so "totally hosed" for us may have a very different definition.
What do you mean by "very large numbers of columns" ? I've seen some mongo users with very rich, i.e. large, document models.
1,000s, 10,000s, 100,000s, millions. MongoDB columns are designed for serialization of rich documents, not store unbounded ranges of data values.
Even without tens of thousands of concurrent users, you'll eventually run into a deeply critical performance wall when MongoDB starts reading from disk. It's really best to think of it as an in-memory database.
Comments
happily, this is not a synchronous application with tens of thousands of concurrent users, so "totally hosed" for us may have a very different definition.
What do you mean by "very large numbers of columns" ? I've seen some mongo users with very rich, i.e. large, document models.
1,000s, 10,000s, 100,000s, millions. MongoDB columns are designed for serialization of rich documents, not store unbounded ranges of data values.
Even without tens of thousands of concurrent users, you'll eventually run into a deeply critical performance wall when MongoDB starts reading from disk. It's really best to think of it as an in-memory database.