[ffsm8]

> We successfully scaled MongoDB from a few users a day to millions of queries an hour.

Uh, 1 query per second is 60x60x60=216000... Soo, 1 million queries per hour equals 4-5 queries per second.

Soo, that's not even at toy project level. That's extremely low scale, like the smallest possible instance small.

A consumer laptop does 20+k queries/seconds on postgres, mysql etc. a raspberry pi usually still gets 1-3k read queries/s, depending on the used SD card (Or 432 million queries per second).

You're not instilling any kind of confidence quoting numbers like that

[twentythree-at]

60x60x60 is 60 hours, not 1 hour. 1 hour is 3600 seconds. therefore 1 million queries per hour equal ~280 queries per second.

[ffsm8]

Oof, you're right. Still within the performance profile of a raspberry pi though, even if it's no longer off by an order of magnitude

So I think my point still stand: that number is as low as you can get for any rdbms.

[adityapatadia]

TBH we are at around 15M queries per hour. I am sure our customers don't want us to run on RPi. Btw, it's not only query but billion+ rows which are also there.

[ffsm8]

I expected as much, usually it's me pointing out that mongodb is a decent DB depending on the data you're ingesting/storing, and it's builtin clustering is significant better then what postgres offers at the moment.

But the number was so low I couldn't help but point out that this was more likely to convince me that mongo is a joke then a usable database

[endisneigh]

Your math is wrong… and it cannot be assumed that traffic is uniformly spread.

Finally what you’re saying is orthogonal to MongoDB - you can self host Mongo on a raspberry pi.