First time posting a question here and a noob with mongo. Apologies if question = stupid.
I have an application that needs to be able to run on a local computer, even if that computer loses connection to the local network. The application will be used in a very small organisation … and in the event they have issues with their local network (switch failure eg.), the application still needs to work. The application uses a local mongo database. On the other hand, the application is designed to be able to being used in much larger organisations as well, with multiple clients, even in different sites connecting to the same database. Even in this situation, the requirement is still that the application must be able to run without network connection in case of serious network problems. So every client needs at least a working (read-write) local replica.
To add some redundancy, easy backup and scale up the app, I started testing with replica sets. As long as the client computer is connected to the network, this works great. I can add more nodes, make backups, datadumps, have some offsite replica’s etc. But the problem is that as soon as the client computer loses network connection, the local database (primary) goes into read-only (secondary). I can add as many nodes as I want … from what I understand, in this situation, the local database will always become readonly, even if that member was primary before the connection was lost.
My question is … is there a solution for this problem? Is there maybe another way to accomplish what I need, besides replica sets?
Thanks for the infomation