Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Hobo424353yReally? I thought it was all about scaling? (I know bare minimum about it)
viking818443yDon't know who that expert is, but it's a vague response..
Using MongoDb for a little blog, is like building a villa to store your peanuts.
Whenever it comes to large datasets - it's a matter of how you store, use and maintain it. Usually you would store everything raw, then run queries on that to generate reports. Live queries will run slow on huge datasets regardless of technology. Aggregated reports (documents) that are appended as data changes is what you will query upon to your end user. Typically, specialized reports suited for the task at hand.
Not knowing your data, but you can't expect instant result on something that can't be stored in memory and require different documents/collections to join.
And.. Don't use a single server instance for everything. Your raw storage should be kept alone. Optimize your report servers for read.
MySQL (Maria DB) for life...