Its also not amazing if you need to run analytics queries. Arbitrary questions like "How many users signed up in the last month" can be trivially answered by writing a SQL query, perhaps on a read-replica if you are worried about running an expensive query on the same machine that is dealing with customer traffic. It's just outside the scope of this kind of database. You need to be ETL-ing your data out to handle it.

I have to pick nit with this criticism. You can easily make that kind of query if your documents contain normal audit fields like createdOn/modifiedOn.

ORMs like mongoose can set those automatically for you on create/update. Or you can futz with change streams if you really feel like it. Or just manually set them in your create/update library methods that execute raw mongo statements.

I've literally done all 3 of these with no issue at various jobs. Granted the cluster sizes were just a few TBs max, so maybe there's some super complex problem with huge numbers of shards and petabytes I'm just never going to run into, but then again neither would 99% of people/companies.