scottalanmiller

scottalanmiller

We had tried Solr and didn't find it any better than the default. They were both quite bad. So w settled on the default because it doesn't break from time to time like Solr did.

scottalanmiller

An interesting comparison of ML and EXODO, look at the past month popular posts. I think EXODO gets a lot more threads, ML gets a lot more posts per thread. But EXODO might have a lot of historically imported posts, so maybe they aren't that busy per day?

0_1502289261337_Screenshot from 2017-08-09 09-32-25.png

0_1502289275624_Screenshot from 2017-08-09 09-33-27.png

scottalanmiller

@bartvb said in Biggest nodebb Community forum?:

Still curious about this.

exo.do 930k posts
Bethesda.net 560k posts
Mangolassi.it seems to be at 330k posts now.
https://what.thedailywtf.com/ is at 300k

You would think that there are sites out there that crossed the 1MM mark?

Yup, ML is just about at 330K

0_1502288984426_Screenshot from 2017-08-09 09-29-15.png

A lot of the busy communities imported posts from elsewhere so may not have an ingest rate to get them to 1mm quickly. Hard to say. Seems like Exo will be there in no time, though.

scottalanmiller

@Bri said in MongoDB reliability called into question?:

Something else I've been looking at are graph databases like Neo4j and Arango, and now I'm kind of anticipating that you're going to tell me that it's in the same boat (i.e. old tech with a new name)

Nope, old with still with the old name Graph databases are known to go back to at least 1969.

scottalanmiller

@Bri said in MongoDB reliability called into question?:

@scottalanmiller said in MongoDB reliability called into question?:

NoSQL pre-dates relational data, I've been a NoSQL engineer since 1989 and it was OLD then

That's an interesting tidbit, what was it called before NoSQL and what were the technologies?

Well it didn't have a specific name, if you wanted to refer to it as a category you might have called them non-relational databases, but the idea of making them a category didn't exist. NoSQL refers to such a broad set of things that it doesn't mean much, just that it isn't relational theory. Even today, talking about NoSQL is a bit silly since it includes so many unrelated things. NoSQL only exists as a reaction to so many people thinking that relational was the only thing that there was an just making crazy assumptions. It's kind of a movement of "reconsider how you want to store data."

There were still lots of different kinds of things... flat files, hierarchical, graph and such. I'm not sure, but document databases might be newer.

scottalanmiller

My guess is that this is people who don't understand their database and have built it incorrectly for their needs. MongoDB under some circumstances is not supposed to return all records. If you want that guarantee you either need to architect your database for it or use a database that guarantees it under all conditions. This is not a reliability issue with MongoDB unless these guys produce something a lot more substantial that rumours. MongoDB is pretty good, we've had it in production at some decent scale for three and a half years and I use it in numerous places, not only with NodeBB.

If you are looking for random threads of anonymous people posting "concerns" about things that they don't understand about any database, you can find it. Everyone tied to one product likes to have "concerns" about the products that they didn't choose or don't support (or sell.) I would take this with a grain of salt. If you look at the rest of that thread, it's a joke. People who clearly don't understand data theory and use cases or schemas or relational data just ranting because they hate the idea of "new" even when it is quite old (NoSQL pre-dates relational data, I've been a NoSQL engineer since 1989 and it was OLD then - we just didn't this cool retro name for it.)

With any database, it's worth knowing if there are issues. But MongoDB is a leader and absolutely perfect for this use case. The problem with the people in that thread is that they are looking for relational systems that are not sharded and are full synchronous across shards all of the time, choose something that they didn't understand that was the wrong tool for the job and instead of admitting that they were confused and goofed on their selection they rail against the product.