networkless version of the server (or MongoDatabase)

[asereda-gs]

Hello,

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.

[bwaldvogel]

There are no such plans. The focus of this project is to provide a Java implementation that speaks the wire protocol.

What’s the problem with having a @ClassRule?

[asereda-gs]

The focus of this project is to provide a Java implementation that speaks the wire protocol.

This requirement is not contradictory to the original aim of the project. You can still have network layer on the top of existing "backend". Sometimes it is easier to use lightweight / embedded version of the product without connection protocol (eg. h2).

What’s the problem with having a @ClassRule?

That means you have to have static variable and manually manage the state (eg. drop database before/after test). Plus one can't run tests in parallel.

[bwaldvogel]

This requirement is not contradictory to the original aim of the project. You can still have network layer on the top of existing "backend".

Feel free to submit a PR if you have an idea how to achieve it.

[asereda-gs]

Is it acceptable if core module depends on mongo java driver ?

[bwaldvogel]

Unfortunately it’s not an option. Users of mongo-java-server would get a transitive dependency on mongo-java-driver in probably a different version.

[markbigler]

Is it acceptable if core module depends on mongo java driver ?

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 as Fongo (https://github.com/fakemongo/fongo/). You may have to make adjustments for each new version of mongo java driver and support the old versions as well.

• Support for java mongodb driver 3.6.4+ fakemongo/fongo#357
• fongo not compatible with 3.7 driver version fakemongo/fongo#337
• Fongo v2.2.0-RC2 incompatibility with mongodb driver v3.9.1 fakemongo/fongo#367
• many more

I think that for this reason Fongo is no longer maintained and many people use mongo-java-server instead.

[asereda-gs]

Yes, that's a valid point.