2 ms·
I think you're trolling but in case you aren't: structured logging, distributed cache, heterogenous analytics. You might prefer other solutions to each just as
by paulddraper 9y ago
I think you're trolling but in case you aren't: structured logging, distributed cache, heterogenous analytics.
You might prefer other solutions to each just as I prefer technologies other than Perl, but "no purpose" is incorrect.
- gaius 9y agoThere are better solutions to all of those use cases. Logging? ELK. Cache? Redis. Not sure what you mean by "heterogenous analytics" but that's usually a layer on top of whatever data store you choose, and we've established that MongoDB just isn't a good data store.
- user5994461 9y agoIt's not trolling. MongoDB really doesn't have a purpose. There is nothing it is good at. https://thehftguy.com/2017/03/29/whats-the-best-nosql-database-cassandra-vs-mongodb-vs-redis-vs-elasticsearch/ https://thehftguy.com/2017/03/29/whats-the-best-nosql-databa... logging => elasticsearch distributed cache => memcache analytics => any SQL database for low volume (< 1TB). any data warehouse database for high volume (> 10TB).
- paulddraper 9y ago"Memcache" Requires holding all data in RAM. Loses all data on a restart. Can't cache values more than 1mb. (Not that these are necessarily terrible; they're limitations that may not be appropriate for all uses.) "Don't use mongo, use any data warehouse database" That's what I suggested; you just turned it into an abstract recommendation.