187 engineers on Hacker News describe using MongoDB first-hand: 60 endorse it, 36 regret it, 25 are mixed.
“Riak passed our test at that time, MongoDB didn't.”
regret · personal · rmetzler · 2024-11-20 · source ↗ · wrong label?“The change streams are awesome and has let us create a unified trigger system that works outside of the database”
endorse · production · christkv · 2024-08-17 · source ↗ · wrong label?“Have previously been a heavy MongoDB user but when we migrated to Postgres... it just made querying so much easier and reliability has been great.”
regret · production · webprofusion · 2024-07-08 · source ↗ · wrong label?“Since MongoDB is so cheap, quick, and easy to get going my team tends to make that the default option. In many cases we've been able to run for years on MongoDB.”
mixed · production · taylodl · 2024-06-27 · source ↗ · wrong label?“When we moved to mongo performance never recovered.”
regret · production · QuadmasterXLII · 2024-03-11 · source ↗ · wrong label?“The first one was the MongoDB/NoSQL hype... I tried it in a medium sized project and burnt my finger”
regret · personal · neya · 2024-03-03 · source ↗ · wrong label?“I used MongoDB from the start, but I'm beginning to regret that - It's getting hard to maintain relational consistency”
regret · personal · 3 yr · varun_ch · 2023-12-22 · source ↗ · wrong label?“We use MongoDB in conjunction with RealmDB to build an offline first mobile app. For this specifically it works very well.”
endorse · production · DandyDev · 2023-12-17 · source ↗ · wrong label?“the size of the MongoDB clusters meant that expenses never again made sense for the revenue that Flowdock brought in.”
regret · production · wzm · 2022-04-08 · source ↗ · wrong label?“for these we actually store in mongo since they work best there”
endorse · production · ra-mos · 2021-12-27 · source ↗ · wrong label?“we winded up using MongoDb and it turned out to be fast, scalable, had mature tooling and we can keep tons of event related metadata in it”
endorse · production · SMFloris · 2021-02-24 · source ↗ · wrong label?“I loved working with mongo, although it gets slow overtime but it was enjoyable.”
mixed · production · amir734jj · 2020-11-26 · source ↗ · wrong label?“Ran into this yesterday in prod, and it broke stuff. We are paying Mongo support customers, and support's answer is”
regret · production · vosper · 2020-11-04 · source ↗ · wrong label?“we replaced Kafka with Change Streams( little over 7k messages per second) and ES with text search (2K queries per second) in MongoDB”
endorse · production · truth_seeker · 2020-06-15 · source ↗ · wrong label?“since MongoDB was a pain to use for other reasons, I have never felt the slightest inclination go back”
regret · production · madhadron · 2019-09-23 · source ↗ · wrong label?“we know it sucks, dislike using it, don't have the significant resources needed to get off.”
mixed · production · vosper · 2019-09-02 · source ↗ · wrong label?“someone logged into mongodb and dropped all the tables and backups were not test before, so they did not work.”
regret · production · InGodsName · 2018-12-27 · source ↗ · wrong label?“This happened to us numerous times before and after we migrated to their Atlas platform.”
regret · production · kailuowang · 2018-12-19 · source ↗ · wrong label?“MongoDB is actually the best database I have ever used in production, in question of both performance AND scalability.”
endorse · production · dejaime · 2018-11-03 · source ↗ · wrong label?“Now we just run our own VMs with our own Mongo instances and curse the day we were obligated to move to Azure.”
endorse · production · fatbird · 2018-10-17 · source ↗ · wrong label?“mongodb - which I love and use daily, but would never, ever have chosen over Oracle for high transaction bitcoin exchange.”
endorse · production · ghshephard · 2017-12-23 · source ↗ · wrong label?“MongoDB was a good drop-in replacement with only 20-30 extra lines of code.”
endorse · production · Kpourdeilami · 2017-11-16 · source ↗ · wrong label?“We struggled with most, but we used or test MongoDB, Cassandra (including ScyllaDB)”
regret · personal · doh · 2017-10-05 · source ↗ · wrong label?“Since 2012, that's when we upgraded to 2.0, we had 10 min of total downtime. That's 99.999% uptime in 5 years.”
endorse · production · 5 yr · rfehrmann · 2017-07-07 · source ↗ · wrong label?“It's ridiculous that Mongo doesnt have this kind of transactional backup appratus. But we needed time-series data storage. And mongodb was pretty much it.”
mixed · production · kefka · 2017-06-03 · source ↗ · wrong label?“Choosing Mongo for our main data store has caused us more problems than it solved... After running this in prod for 3 years, we have a strong opinion on this”
regret · production · 3 yr · parisk · 2016-12-01 · source ↗ · wrong label?“The whole product started as a NodeJS+MongoDB app, which was a disaster at scaling to the billions of requests a day we handle and we've replaced it everywhere”
regret · production · Eridrus · 2016-10-16 · source ↗ · wrong label?“We run Mongo side by side with PG, and even though the PG is just replicated... Mongo was more easy to configure.”
mixed · production · tinco · 2016-10-06 · source ↗ · wrong label?“MongoDB is the worst when having to do, well, anything with it.”
regret · production · lykron · 2016-07-05 · source ↗ · wrong label?“My company used mongo for years before we got our shit together. Schmemas were always implicit”
regret · production · red_hare · 2016-06-08 · source ↗ · wrong label?“Use of MongoDB at PlanGrid is probably the single worst technical decision the company ever made.”
regret · production · xenadu02 · 2016-06-07 · source ↗ · wrong label?“it was a MAJOR ops headache because it would NEVER finish. Never again mongo for anything with lots of writes.”
regret · production · dev360 · 2016-02-04 · source ↗ · wrong label?“When we chose MongoDB for a project, a dominant criterion was out of the box geo queries.”
endorse · production · sriku · 2015-11-13 · source ↗ · wrong label?“We moved away from Mongo for very similar reasons, but we moved to Cassandra instead of Postgres only with great trepidation”
regret · production · squidlogic · 2015-11-06 · source ↗ · wrong label?“We use mongodb for it's scalability, json handling strategy.Good community support for it's growth in future”
endorse · production · _navaneethan · 2015-08-03 · source ↗ · wrong label?“We use MongoDirector for our production Mongo instances and it's been great. No issues since we switched to them in September 2014.”
endorse · production · 1 yr · exhilaration · 2015-07-23 · source ↗ · wrong label?“We've been using Mongo to store our authentication info, and to store payment transactions. No major problems so far, but our needs fit nicely into what MongoDB can provide.”
endorse · production · vhogemann · 2015-07-21 · source ↗ · wrong label?“I, well, one my companies, have been using mongo for a while without any problems... it served us well.”
endorse · production · _pdp_ · 2015-07-19 · source ↗ · wrong label?“I'm torn about these choices, I've tried and liked them, but am a bit out of my element as primarily a python/c developer.”
endorse · personal · mixmastamyk · 2015-06-14 · source ↗ · wrong label?“I once wrote a few million records into Mongo. It was consistent before the write, but never again after.”
regret · personal · cpks · 2015-04-22 · source ↗ · wrong label?“Mongo is a young database, with some super obvious flaws and growing pains.”
mixed · production · spimmy · 2015-04-22 · source ↗ · wrong label?“We have ~12 nodes in our mongo cluster, and havent had a single issue with these nodes.”
endorse · production · samstave · 2015-03-16 · source ↗ · wrong label?“it is schemaless so we are no longer constrained by DBAs... the schema is now part of your [application]”
mixed · production · takeda · 2015-01-05 · source ↗ · wrong label?“deploying MongoDB into production and we've never had any real issues”
endorse · production · s_kilk · 2014-12-20 · source ↗ · wrong label?“Other than this issue, MongoDB has been pretty good... We have MongoDB cluster setup and it has saved us a number of times.”
endorse · production · bhouston · 2014-12-20 · source ↗ · wrong label?“Incidentally, this is why we moved to TokuMX over vanilla Mongo; ... document locking means that I practically never have to worry about lock contention”
regret · production · cheald · 2014-12-17 · source ↗ · wrong label?“We've been using Mongo for all the core functionality at TrackIf.com and are still very happy with it.”
endorse · production · ecaron · 2014-12-11 · source ↗ · wrong label?“I've really enjoyed using mongodb and find it fast and eminently suitable for a problem domain like CRM that is constantly in transition.”
endorse · production · greggdourg · 2014-10-25 · source ↗ · wrong label?“I use MongoDB when developing a common app for NodeJS because NodeJS simply works very well with MongoDB”
endorse · production · nielskrijger · 2014-10-19 · source ↗ · wrong label?“it's ability to not totally fall apart under load (in fact performing really well)”
regret · production · bdeggleston · 2014-08-04 · source ↗ · wrong label?“We switched from SQL to Mongo on http://versus.com one year ago and are quite happy—we couldn't imagine to go back.”
endorse · production · 1 yr · versusdotcom · 2014-04-25 · source ↗ · wrong label?“While our experience with Cassandra is by and large much more performant and cost effective than MongoDB, getting setup with Cassandra was not as easy with MongoDB.”
mixed · production · nemothekid · 2014-03-31 · source ↗ · wrong label?“I've been using mongo for about a year. The only pain points are that the API documentation is somewhat confusing.”
mixed · personal · 1 yr · mjhea0 · 2013-12-17 · source ↗ · wrong label?“I have not had to touch the system since it was put in production over a year ago - it just runs.”
endorse · production · 1 yr · larsmak · 2013-12-06 · source ↗ · wrong label?“after many replica set/sharding bugs springing up, I am less inclined to use it. That was the major feature we used if for.”
regret · production · specialp · 2013-12-06 · source ↗ · wrong label?“we use mongo as a document store and use its SQL like querying to generate the paged search results.”
mixed · production · mikegioia · 2013-11-26 · source ↗ · wrong label?“prototyping and testing seems to indicate that MongoDB is up to the task, but we'll see.”
endorse · personal · DigitalSea · 2013-11-12 · source ↗ · wrong label?“I quickly realised that i should use a relational store and my problems were solved quickly with postgres.”
regret · personal · nashequilibrium · 2013-11-11 · source ↗ · wrong label?“we're currently migrating off of Mongo to Postgres due to an experience similar to the OP's.”
regret · production · statenjason · 2013-11-11 · source ↗ · wrong label?“MongoDB is fine db for certain scenarios and I am using it in production.”
mixed · production · desireco42 · 2013-11-07 · source ↗ · wrong label?“Here's a list of open questions I have about MongoDB in production”
regret · production · calpaterson · 2013-10-29 · source ↗ · wrong label?“I use MongoDB now in production and I am happy about it.”
endorse · production · annnnd · 2013-10-21 · source ↗ · wrong label?“Mongo is definitely a flawed product, but why should I care about the clownshoeness of its mmapped files when it has given us so much for so long?”
mixed · production · rgo · 2013-10-20 · source ↗ · wrong label?“Data sets larger than 100GB are no problem either -- right now I'm running an instance with a 1.6TB database.”
endorse · production · functional_test · 2013-10-20 · source ↗ · wrong label?“The perf-killer on Mongo in this scenario is the write lock.”
regret · production · nemothekid · 2013-08-22 · source ↗ · wrong label?“I've been using MongoDB to start with for quite a while”
endorse · personal · veesahni · 2012-12-29 · source ↗ · wrong label?“99% of our production issues involve bugs in MongoDB and it's inability to effectively use all available resources”
mixed · production · nasalgoat · 2012-12-28 · source ↗ · wrong label?“Every time I've seen it used in production, it always seems like its being used as an improperly implemented RDBMS or an improperly implemented key+value store.”
regret · production · freework · 2012-12-26 · source ↗ · wrong label?“it's a good enough fit, in-place updates can be really handy and we prefer not having 2 different databases.”
endorse · production · bobfunk · 2012-12-26 · source ↗ · wrong label?“I'm hoping this'll be a viable replacement for MongoDB.”
regret · personal · codewright · 2012-11-09 · source ↗ · wrong label?“Mongo lies about being ready after an initial install.”
regret · personal · Pewpewarrows · 2012-11-05 · source ↗ · wrong label?“It plays a lot more smoothly with MongoDB and I find it far simpler to hook into more modern functionality”
endorse · production · imothee · 2012-10-01 · source ↗ · wrong label?“The 2GB 32-bit limit of MongoDB seems like a complete non-issue to me.”
endorse · personal · werkshy · 2012-09-25 · source ↗ · wrong label?“We've been using MongoDB in production for our main content store at Conversocial for over a year now.”
endorse · production · 1 yr · colinhowe · 2012-09-25 · source ↗ · wrong label?“At our company we have a much bigger MongoDB dataset in production.”
regret · production · 23david · 2012-09-25 · source ↗ · wrong label?“We stopped using it in production and moved to Solr. I don't hate MongoDB but I think it is overhyped.”
regret · production · pbharrin · 2012-09-25 · source ↗ · wrong label?“we're using MongoDB about 3 years in production at this point, but we're far from happy about the availability it provides”
mixed · production · 3 yr · stingraycharles · 2012-09-17 · source ↗ · wrong label?“For example I fetch one User object (with all the user's data self contained) from the database and do everything client side. So in my case MongoDB works perfect.”
endorse · production · taligent · 2012-08-29 · source ↗ · wrong label?“after going through our internal cost of resolving these issues versus rewriting our app to use Mongo we decided on the latter. We haven't looked back since...”
endorse · production · wrath · 2012-08-19 · source ↗ · wrong label?“We have been using MongoDB with pretty good success. Our multi-shard DB has 3 servers per replica set”
endorse · production · explodingbarrel · 2012-06-30 · source ↗ · wrong label?“I have used MongoDB with great sucess as the canonical store of documents which are then indexed in a full-text search engine”
endorse · production · pixelmonkey · 2012-04-14 · source ↗ · wrong label?“we have been using MongoDB since version 1.5 and found it incredibly useful addition to our toolbox.”
endorse · production · old-gregg · 2011-12-31 · source ↗ · wrong label?“I've even been using it on Windows and found it to be very well behaved indeed. Same goes for MongoDB for that matter.”
endorse · personal · krmmalik · 2011-12-08 · source ↗ · wrong label?“I made this mistake with MongoDB, however.”
regret · production · cmer · 2011-11-07 · source ↗ · wrong label?“I've been using MongoDB for well over a year now in around 6 apps... we've had data disappear, recurring random crashes, ect. ... I love MongoDB and I would still use it”
mixed · production · 1 yr · matthewcford · 2011-11-07 · source ↗ · wrong label?“We've been using Mongo for almost a year now, and we've not seen any of the major issues such as data loss referred to.”
endorse · production · 1 yr · wedgemartin · 2011-11-07 · source ↗ · wrong label?“We use MongoDB in production and all the issues we've encountered have been either environment or configuration related.”
mixed · production · bitops · 2011-11-07 · source ↗ · wrong label?“Currently we have dozens of MongoDB instances across several different data clusters storing over a TB of data and handling 10s of thousands of requests per second”
endorse · production · 1.5 yr · harryh · 2011-11-06 · source ↗ · wrong label?“I've used MongoDB in production since the 1.4 days. It should be noted that my apps are NOT write heavy. But, many of the author's points can be refuted by using version 2.0.”
mixed · production · jonpaul · 2011-11-06 · source ↗ · wrong label?“I've been using Mongo now (currently using 1.8) for three years, 2 million hits/day, with a replicated set, and while I've needed maintenance”
endorse · production · 3 yr · Goldcap · 2011-11-06 · source ↗ · wrong label?“I've been using MongoDB for about 5 months now and can say that it is an excellent tool.”
endorse · personal · 0.4 yr · hackDaily · 2011-10-31 · source ↗ · wrong label?“hitting 10,000 impressions per second at peak ties. This is all on one box and it hasn't broken a sweat yet.”
endorse · production · james33 · 2011-10-31 · source ↗ · wrong label?“We have been using MongoDB in a production environment for almost a year and half now. It's great but there are some serious issues”
mixed · production · 1.5 yr · wtf242 · 2011-10-31 · source ↗ · wrong label?“it wasn't until we switched to MongoDB that we had to buy more servers.”
regret · production · rfurlan · 2011-10-25 · source ↗ · wrong label?“horizontal scaling wasn't our only issue with MongoDB.”
regret · production · schmichael · 2011-06-22 · source ↗ · wrong label?“I love Mongo, but I've been burned enough trying to use it on various projects to make sure I (or my company) have a solid reason”
mixed · production · ddemaree · 2011-06-17 · source ↗ · wrong label?“MapReduce...sadly it's single threaded, but whether you are doing real-time reporting”
mixed · production · latch · 2011-05-17 · source ↗ · wrong label?“mongo is best for just about everything else that doesn't hold the data in MySQL.”
endorse · production · RyanAmos · 2011-03-09 · source ↗ · wrong label?“We switched back to more reliable master/slave setup finally. So before trying sharding, you should watch this video”
regret · production · stoneg · 2011-01-28 · source ↗ · wrong label?“I introduced this new technology to the company I work at which has now adopted it for two significant projects.”
endorse · production · kingnothing · 2010-12-31 · source ↗ · wrong label?“I particularly want to mention the simplicity of setting up the database and using the API.”
endorse · personal · kefeizhou · 2010-12-31 · source ↗ · wrong label?“one of the great things about MongoDB is that, in some cases, you can easily afford to lose 1 minute worth of inserts”
mixed · production · latch · 2010-12-23 · source ↗ · wrong label?“using an autosharded mongodb cluster in production for writing and reading analytics data for our apps... so far its going great.”
endorse · production · kingnothing · 2010-12-07 · source ↗ · wrong label?“I use MongoDB for greenfield app development and experiments, so I can quickly alter "tables" and "attributes", without having to bother with first thinking about schema”
endorse · personal · psadauskas · 2010-12-06 · source ↗ · wrong label?“If you're already using MongoDB, it's really dead-easy to setup (see the docs).”
endorse · production · thibaut_barrere · 2010-10-28 · source ↗ · wrong label?“I've been using MongoDB for well over a year... it's so nice to develop on top of. It's a joy to use.”
endorse · personal · 1 yr · luigi · 2010-10-26 · source ↗ · wrong label?“I've been using MongoDB in production for the last eight months and I now consider myself an idiot for having wasted time with it”
regret · production · 0.67 yr · saurik · 2010-10-26 · source ↗ · wrong label?“We switched to a local mongodb server as a near drop-in replacement, and it was a billion time faster and more efficient.”
endorse · production · perezd · 2010-10-24 · source ↗ · wrong label?“It uses MongoDB capped collections to keep the number of stored entries to a manageable level. We use the hell out of it.”
endorse · production · mojombo · 2010-10-18 · source ↗ · wrong label?“The company I work at has been using Mongo for a while, and anytime we've had an issue, Eliot has been right there to help us.”
endorse · production · tmountain · 2010-10-08 · source ↗ · wrong label?“We're using MongoDB in production and have a few boxes setup... I find that pretty amazing.”
mixed · production · tmountain · 2010-09-14 · source ↗ · wrong label?“I'm using MongoDB in production and I've looked at your documentation a bunch.”
mixed · production · cbryan · 2010-07-08 · source ↗ · wrong label?“We run MongoDB on development machines... In our experience, MongoDB single-node recovery is very robust.”
mixed · personal · ekidd · 2010-07-08 · source ↗ · wrong label?“Been running it in production for 3 months, working fine.”
endorse · production · 0.25 yr · cgbystrom · 2010-07-07 · source ↗ · wrong label?“We've been using MongoDB for over a year in production having started at v0.9 and now using only stable releases”
mixed · production · 1 yr · dmytton · 2010-06-22 · source ↗ · wrong label?“I have a complex mongodb install in production with no problems.”
endorse · production · oldgregg · 2010-06-15 · source ↗ · wrong label?“I've been running MongoDB in Production since last August... With almost a year of uptime I've had no data loss or anything else.”
endorse · production · 1 yr · rit · 2010-06-15 · source ↗ · wrong label?“I use it in production on http://www.ocwsearch.com/. Short answer: it's awesome.”
endorse · production · pierrefar · 2010-05-31 · source ↗ · wrong label?“I have been in production w/ MongoDB since August '09 and it was a huge performance improvement over MySQL.”
endorse · production · 1 yr · rit · 2010-05-12 · source ↗ · wrong label?“We haven't had a single problem with Mongo or API interfaces.”
endorse · production · 0.7 yr · rit · 2010-03-25 · source ↗ · wrong label?“overall, it was kind of nice (coming from Mongo)”
neutral · production · red_hare · 2024-11-19 · source ↗ · wrong label?“We heavily use microservices but we have a well defined stack. Python/gunicorn/flask/mongodb with k8s.”
neutral · production · orochimaaru · 2023-10-30 · source ↗ · wrong label?“I went with what my last profitable side project used - mongodb.”
neutral · personal · lightning19 · 2023-03-11 · source ↗ · wrong label?“we run several stateful workloads, including ElasticSearch and MongoDB, in GKE.”
neutral · production · anchochilis · 2022-08-12 · source ↗ · wrong label?“we replaced the in-built MongoDB with GraphQL.”
neutral · production · indymike · 2022-06-13 · source ↗ · wrong label?“We use CityNetwork public cloud managed services (MongoDB, Rancher/Kubernetes and Openstack for edge network/load balancer)”
neutral · production · permb · 2021-12-15 · source ↗ · wrong label?“When we migrated from Mongo to Document there were quite a few queries that failed to run”
neutral · production · tpxl · 2021-11-02 · source ↗ · wrong label?“We're using Next.js at my current company with a custom MongoDB based CMS.”
neutral · production · fbrchps · 2021-09-07 · source ↗ · wrong label?“The main cloud services I use at work are: 2. DocumentDB/CosmoDB/Cloud Atlas”
neutral · production · gravypod · 2020-08-16 · source ↗ · wrong label?“We have a Java + Mongo stack and recently we had an issue in prod”
neutral · production · theanirudh · 2020-03-11 · source ↗ · wrong label?“let's say that I need to setup a MongoDB Replicaset... the playbook takes care of everything”
neutral · production · lewaldman · 2019-10-29 · source ↗ · wrong label?“I've been given js+mongo apps by partners that I had to modify to use standard postgres before becoming responsible for herding them in prod.”
neutral · production · sneak · 2019-05-10 · source ↗ · wrong label?“a payment batching system built ( not by me ) with a MongoDB database failed to work correctly because the aggregation query was checking a field was null”
neutral · production · ajxs · 2019-02-11 · source ↗ · wrong label?“I have used MSSQL, MySQL, PostgreSQL, Mongo and Cassandra all as primary data stores.”
neutral · production · davismwfl · 2018-12-28 · source ↗ · wrong label?“the expected cost savings from not paying for OpsManager/Mongo support”
neutral · production · wftglf · 2018-12-20 · source ↗ · wrong label?“7 servers for Mongo (same as above)”
neutral · production · scarface74 · 2018-11-08 · source ↗ · wrong label?“I built the prototype in 'Record Time (TM)' with MongoDB”
neutral · personal · nevi-me · 2018-07-02 · source ↗ · wrong label?“You can send your Linq expression to sql Server, Mongo etc in production and mock out your source in your unit tests”
neutral · production · scarface74 · 2017-12-05 · source ↗ · wrong label?“I was tech lead on a migration of two much larger Mongo collections to sharded Mongo.”
neutral · production · jhwjhw · 2017-08-09 · source ↗ · wrong label?“have our data services (Elasticsearch, Cassandra, MySQL, MongoDB) join the rest of our apps on Kube-orchestrated infrastructure”
neutral · production · chrissnell · 2016-12-22 · source ↗ · wrong label?“The event logs are parsed with Fluentd and saved in a mongodb instance.”
neutral · production · rhapsodyv · 2016-12-19 · source ↗ · wrong label?“For development environments we are running MSSQL, Elasticsearch, Mongo, Kafka”
neutral · production · paultyng · 2016-11-01 · source ↗ · wrong label?“We had a lot of operational experience with Mongo from our previous jobs at Atlassian, and started out storing almost everything in Mongo.”
neutral · production · jkodumal · 2016-09-09 · source ↗ · wrong label?“I reads content from a parse-server (MongoDB), builds the html and uploads to AWS S3.”
neutral · production · bikamonki · 2016-05-29 · source ↗ · wrong label?“I spent almost two weeks deciding between mysql and mongodb. Ultimately went with mongodb but it's not my forte.”
neutral · production · sph130 · 2016-04-15 · source ↗ · wrong label?“we started out using MongoDB, and eventually we migrated to Datomic”
neutral · production · sdegutis · 2015-12-01 · source ↗ · wrong label?“We run a sharded+replicated mongo cluster and a redundant postgresql array in docker containers.”
neutral · production · tinco · 2015-11-22 · source ↗ · wrong label?“We're running on a free tier MongoLab database. If we get spammed or it really takes off, that's going to disappear.”
neutral · production · z1mm32m4n · 2015-07-03 · source ↗ · wrong label?“MongoDB and server logic is separated from the client-side view rendering”
neutral · personal · liamzebedee · 2015-07-01 · source ↗ · wrong label?“I think our installations of nginx[1], Python[2], pip[3], rust[4], mongo, consul[4], openldap[1], gcc[3]”
neutral · production · deathanatos · 2015-03-31 · source ↗ · wrong label?“scale resources vertically, similar to how we start with MongoDB”
neutral · production · mrkurt · 2015-01-06 · source ↗ · wrong label?“Our data store is mongo so we use documents for the subscription details”
neutral · production · davismwfl · 2014-12-17 · source ↗ · wrong label?“we use MongoDB with 3 member replica sets even for small deployments. It's easy, built in, works fine with all official drivers.”
neutral · production · eknkc · 2014-11-17 · source ↗ · wrong label?“It was because of our MongoDB service provider. Our oplog instance was offline.”
neutral · production · scorpwarp23 · 2014-09-07 · source ↗ · wrong label?“~$750/mo for one MongoDB replicaset is far, far too much.”
neutral · production · mikegioia · 2014-07-31 · source ↗ · wrong label?“now we just use Postgres, MySQL, MongoDB, etc. etc.”
neutral · production · pedalpete · 2013-12-18 · source ↗ · wrong label?“I just trying to compare with my current stack spring mvc 3, spring data mongodb.”
neutral · production · octix · 2013-12-16 · source ↗ · wrong label?“I've been using mongo for a few years now, can you please elaborate more on better designed mongo and troublesome mongo?”
neutral · personal · 3 yr · octix · 2013-12-16 · source ↗ · wrong label?“MongoDB (which we use in production) isn't currently listed.”
neutral · production · danudey · 2013-11-20 · source ↗ · wrong label?“I didn't realize the MongoDB library we are using wasn't suppressing those types of errors out in production.”
neutral · production · zachflower · 2013-10-30 · source ↗ · wrong label?“Application does not work with node.js MongoDB driver, it still goes through thin minimongo layer, which hides most of the driver API.”
neutral · production · joecarpenter · 2013-10-08 · source ↗ · wrong label?“We were storing analytics counters in Mongo and wanted better consistency guarantees.”
neutral · production · mnutt · 2013-08-21 · source ↗ · wrong label?“No, it wasn't around when we switched to MongoDB.”
neutral · production · mattparlane · 2013-04-24 · source ↗ · wrong label?“in our specific scenario the benefits of using MongoDB were outweighed by the difficulties in having to manage two DBMS in parallel”
neutral · production · julian37 · 2012-12-26 · source ↗ · wrong label?“we have only very thin 'models', which are basically just Mongoose wrappers around MongoDB”
neutral · production · jpallen · 2012-12-24 · source ↗ · wrong label?“Mongode (MongoDb-native wrapper)”
neutral · production · nmeyer · 2012-12-16 · source ↗ · wrong label?“We use a combination of geospatial features from our database (MongoDB) and linear algebra”
neutral · production · glennericksen · 2012-11-30 · source ↗ · wrong label?“We're also using MongoDB for an internal reporting application, but don't use it for our service offering.”
neutral · production · natehark · 2012-11-26 · source ↗ · wrong label?“asynchronously parse and insert them in MongoDB”
neutral · production · rishabhdua · 2012-11-16 · source ↗ · wrong label?“I have been using MongoDB for a long time, unfortunately mostly this has been small applications, so you don't really get to test how MongoDB scales.”
neutral · personal · vertis · 2012-11-05 · source ↗ · wrong label?“built a 10 machine Mongo cluster... ran all sorts of benchmarks before ever using it in production.”
neutral · production · base698 · 2012-09-24 · source ↗ · wrong label?“We were running running MongoDB atop EC2 instances. We chose to back MongoDB with EBS because that was the only reasonable way to get base backups.”
neutral · production · mitchellh · 2012-04-13 · source ↗ · wrong label?“updating MongoDB is now just a matter of sending an e-mail to the guys at MongoHQ”
neutral · production · prib · 2011-12-30 · source ↗ · wrong label?“We use mongo on the backend to provide schemaless storage and are building out a set of RESTful apis.”
neutral · production · larubbio · 2011-12-29 · source ↗ · wrong label?“We are already using PostgreSql and Mongodb as as a data storage”
neutral · production · aespinoza · 2011-12-29 · source ↗ · wrong label?“I use mongo in prod; very much a student of the "right tool for the job" school.”
neutral · production · saturn · 2011-11-07 · source ↗ · wrong label?“We use mongodb extensively, but I get the hipster feeling also”
neutral · production · gstar · 2011-11-07 · source ↗ · wrong label?“Our plan if MongoDB wasn't good enough consisted basically of: (1) crying ourselves to sleep”
neutral · production · rfurlan · 2011-10-21 · source ↗ · wrong label?“run against real mongo on occasion (such as say, using embedded-mongo while developing locally and real mongo before pushing to production)”
neutral · production · thegdb · 2011-07-12 · source ↗ · wrong label?“some of our unit tests and all of our tools other than the shell already do this”
neutral · production · mathias_10gen · 2011-07-11 · source ↗ · wrong label?“we run a bunch of cron jobs every minute with intense MapReduce queries on mongodb to generate relatively up-to-date analytics.”
neutral · production · SeoxyS · 2011-05-26 · source ↗ · wrong label?“We run all of our MySQL and Mongo slave servers with local RAID-0 ephemeral storage.”
neutral · production · blantonl · 2011-04-24 · source ↗ · wrong label?“At Posterous we use MySQL as a main data store but MongoDB for simple analytics and Redis for set operations around contacts and subscriptions.”
neutral · production · rantfoil · 2010-12-07 · source ↗ · wrong label?“We use Java, MongoDB, Hadoop and embedded Jetty at MetaBroadcast”
neutral · production · johnayres · 2010-11-23 · source ↗ · wrong label?“We also use short names, but find that it's not terrible for readability because we use class constants representing each name”
neutral · production · wanderr · 2010-10-24 · source ↗ · wrong label?“As for MongoDB, we ve been using in production for small insignificant things.”
neutral · production · ankimal · 2010-10-06 · source ↗ · wrong label?