TLDR; MongoDB Atlas on Azure (smaller instances with smaller storage) works but comes with a number of pitfalls you should be aware of. You'd save ...
For further actions, you may consider blocking this person and/or reporting abuse
Does your app require MongoDB / NoSQL in general or you could use PostgreSQL instead?
Could probably make it work with PostreSQL as well, however MongoDB does have some goodies like:
Sure, imagine you have a domain object/aggregate root/whatever called AccountingTransaction, which has some properties like Id, State, CreatedOn, and a list of AccountingEntries, where each Entry has Type (Debit/Credit), AccountId (reference), Amount, Currency. In a standard relational database I would need by default somehow to map this entity to more than 1 table - probably I would create AccountingTransactions and AccountingEntries tables, with 1:N relationship between them, then insert 1 row in the first table and maybe 2-3 rows in the second for a single domain object. Moreover, the inserts must happen in a db transaction. In contrast, in a NoSQL db like MongoDB I am just inserting a single document, which has nested "entries" array inside, without a db transaction ...
Really, PostgreSQL is faster than MongoDB on the same basic hardware (e.g. M20 which is 2 Standard_B2s core + 4GB RAM)? That is really surprising to me, thought PostreSQL needs more to run normally .. Is there something on the Internet which can give me more info on that (testing it myself is quite time-consuming ...) ...
Can't state the same about MongoDB Atlas on Azure. As mentioned in the post, we had quite a few random node failovers, and anyway, every scheduled cluster maintenance requires such ... I would not take a db which does not have a well-tested failover capability, as in the cloud everything can happen any time ...
What about pricing PostgreSQL vs MongoDB Atlas on Azure? Not that the latter is cheap, but I expect the former to be more expensive ..
Rergarding performance
enterprisedb.com/news/new-benchmar...
link.springer.com/article/10.1007/...
Regarding AccountingTransaction, you can use PostgreSQL to store and query JSON and it's also faster than MongoDB from what I read postgresqltutorial.com/postgresql-...
And especially for accounting data updates and queries, breaking AccountingTransaciton to relational tables will provide huge benefits down the road. But even if you don't want do to that, you get the best of both worlds with PostgreSQL.
That being said, accounting and banking are probably the golden use cases for relational databases.