Hi @A_Grikk
Here’s some additional thoughts from me:
- Reading the production notes and ensuring the deployment conforms to the recommended settings is worthwhile. This will ensure minimal issues in the long run.
- The recommended production setup for MongoDB remains a replica set instead of a standalone instance. (minimum of 3 data bearing nodes, sans arbiter). Properly setup, a replica set should be competitive with a standalone instance in terms of performance. Plus, you gain additional features not available in a standalone node such as change streams and transactions.
- Schema design and indexing can make or break MongoDB performance, and optimization methods are very different from tabular databases. So please don’t be discouraged if the typical SQL optimization methods don’t really work. I’m sure people in the community would be able to help you should you have issues with either subjects. Pro tip: be familiar with the explain results to optimize queries and index usage.
Best regards
Kevin