How to configure Nitrite DataGate with MongoDB Cluster using Atlas?

[marcos-zenki]

Can someone help me to know how I should configure the NitriteDataGate so that it can connect to a Mongo DB instance that is hosted in Atlas with a cluster configuration? I currently set the host but it gives me an error:

com.mongodb.MongoSocketException: ........mongodb.net: nodename nor servname provided, or not known
at com.mongodb.ServerAddress.getSocketAddresses(ServerAddress.java:211) ~[mongo-java-driver-3.12.0.jar!/:na]
at com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:75) ~[mongo-java-driver-3.12.0.jar!/:na]
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:65) ~[mongo-java-driver-3.12.0.jar!/:na]
at com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:128) ~[mongo-java-driver-3.12.0.jar!/:na]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:117) ~[mongo-java-driver-3.12.0.jar!/:na]
at java.base/java.lang.Thread.run(Thread.java:1623) ~[na:na]
Caused by: java.net.UnknownHostException: ........mongodb.net: nodename nor servname provided, or not known
at java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) ~[na:na]
at java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Inet6AddressImpl.java:52) ~[na:na]
at java.base/java.net.InetAddress$PlatformResolver.lookupByName(InetAddress.java:1061) ~[na:na]
at java.base/java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1683) ~[na:na]
at java.base/java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:1004) ~[na:na]
at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1673) ~[na:na]
at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1533) ~[na:na]
at com.mongodb.ServerAddress.getSocketAddresses(ServerAddress.java:203) ~[mongo-java-driver-3.12.0.jar!/:na]
... 5 common frames omitted

[anidotnet]

I am deprecating the Nitrite DataGate with Nitrite 4.x. Replication is not a widely used feature in Nitrite. Moreover, rather than having an opinionated replication system, IMO it would be better to let the developer manage the replication with their own choice of database and hosting platform.

I believe, the effort of maintaining DataGate could be better spent elsewhere, but if the community really wants it back in numbers, I'll definitely work on it and bring it back.