Hi @Nand_Sharma1 welcome to the community!
First of all, please note that MongoDB is designed to be operated on a dedicated server, and it’s best to not run different server processes on the same node for performance and consistency purposes.
We using MongoDB standalone instance for our product.
A standalone node is not a recommended setup for a production environment. The basic recommended setup for MongoDB is a replica set.
As mentioned by the page Deploy a Standalone MongoDB Instance:
Use standalone instances for testing and development. Do not use these deployments for production systems as they lack replication and high availability. For all production deployments use replica sets. To learn about replica sets, see Deploy a Replica Set.
How long it should wait for MongoDB server to get ready with stored data?
This would depend on many things, many of them specific to your situation (e.g. disk speed, CPU speed, RAM size, how much data you have, whether a recovery is necessary, whether other processes are busy, or also starting up, etc.), so unfortunately I don’t really have a definite answer for this.
I guess once the server can respond to a hello command with
isWritablePrimary: true, it is ready to accept writes and thus is ready to proceed with normal operation.