Mongo DB - difference between standalone & 1-node replica set : <p>I needed to use Mongo DB transactions, and recently I understood that transactions don't work for Mongo standalone mode, but only for replica sets
(<a href="https://stackoverflow.com/questions/56322333/mongo-db-with-c-sharp-document-added-regardless-of-transaction/56323934#56323934">Mongo DB with C# - document added regardless of transaction</a>).<br>
Also, I read that standalone mode is not recommended for production.</p>

<p>So I found out that simply defining a replica set name in the mongod.cfg is enough to run Mongo DB as a replica set instead of standalone.<br>
After changing that, Mongo transactions started working.<br>
However, it feels a bit strange using it as replica-set although I'm not really using the replication functionality, and I want to make sure I'm using a valid configuration.</p>

<p>So my questions are:</p>

<ol>
<li>Is there any problem/disadvantage with running Mongo as a 1-node replica set, assuming I don't really need the replication, load balancing or any other scalable functionality? (as said I need it to allow transactions)</li>
<li>What are the functionality and performance differences, if any, between running as standalone vs. running as a 1-node replica set?</li>
<li>I've read that standalone mode is not recommended for production, although it sounds like it's the most basic configuration. I understand that this configuration is not used in most scenarios, but sometimes you may want to use it as a standard DB on a local machine. So why is standalone mode not recommended? Is it not stable enough, or other reasons?</li>
</ol>
