networkless version of the server (or MongoDatabase)
See original GitHub issueHello,
We’re using mongo java server for many in-memory tests (with MemoryBackend
). For each test there is a new TCP connection created and closed which uses unnecessary system resources.
The reason it is happening for each test is because we prefer @Rule
over @ClassRule
to avoid static fields in JUnit.
Are there any plans to create lightweight version of the server (or MongoDatabase) without networking ?
Regards.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Connecting to Your Sandbox Cluster from the mongo Shell
While connecting to the cluster I am getting the following error:- MongoDB shell version v4.0.4
Read more >Support for java mongodb driver 3.6.4+ · Issue #357 - GitHub
I've tried to use Fongo with java mongodb driver 3.7.1 and receive this exception (with Java 8): ... networkless version of the server...
Read more >Create an ASIOSocket class that implements SocketInterface
Affects Version/s: None. Fix Version/s: None. Component/s: Networking ... SERVER-23245 Implement a suite of tests for new ASIOSocket class.
Read more >unable to connect to local server with mongodb - Stack Overflow
when I tried mongodb command on my terminal I'm getting this JSON format and its not connecting to local host
Read more >MongoDB - Wikipedia
MongoDB is a source-available cross-platform document-oriented database program. Classified as a NoSQL database program, MongoDB uses JSON-like documents ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m not sure if this is a good idea. Once you have a dependency on the
mongo java driver
, you will run into the same problems asFongo
(https://github.com/fakemongo/fongo/). You may have to make adjustments for each new version ofmongo java driver
and support the old versions as well.I think that for this reason
Fongo
is no longer maintained and many people usemongo-java-server
instead.Yes, that’s a valid point.