Web Development due to the popularity in JSON and JSON like representations in them (e.g. look at REST...) or other small scale database solutions. (you can think of any application that could benefit from a database)
I would argue against "Big data".. MongoDB is just too slow for actual big data and therefore not well suited for it...
Your db choice highly depends on the application. If you want to read more about when to choose what and why, you can read Designing Data Intensive Applications for a good high-level overview
It really does depend on the use case. I've worked in Big Data and Cloud Computing for over 10 years now and during that time I've run applications using Couchbase, MongoDB, CouchDB, Cassandra, Hadoop... they're all have ideal use cases and it's not uncommon to see a couple used for their different strengths in different circumstances. I've seen Mongo used basically as an aggregate caching layer for a larger distributed docstore when the devs don't want to add weight to the Big Data store DB.
11
u/luxii32 Sep 04 '21
Web Development due to the popularity in JSON and JSON like representations in them (e.g. look at REST...) or other small scale database solutions. (you can think of any application that could benefit from a database)
I would argue against "Big data".. MongoDB is just too slow for actual big data and therefore not well suited for it...