Best NoSQL database library for Multi-module Clean Architecture project? Hello folks, I'm having a hard time trying to find a NoSQL database library, which can work with multiple modules that get created (presentation, data, domain) by following the clean architecture pattern. I'd normally use Objectbox if the project specification doesn't necessarily has to be in Clean Architecture. If you have worked on any of your Projects in Clean Architecture pattern with multiple modules, then what databases have you used? 🤔

Clean Architecture explicitly doesn’t care what library you’ll use for your database/anything else. You mention multiple modules, but also presentation/data/domain — only of those should be concerned with specific library used

I understand that, but the problem here lies within the way some of these libraries work. And most of them don't support multi-module projects. As I said, for a single module project I'd prefer to use Objectbox, but it doesn't support Multi-module project, so that's a huge bummer for me 😔 Hence, searching for alternatives that can work well with multi-module project while at the same time acknowledges & respects the S.O.L.I.D. principles in clean architecture

The only reason for any “multi-module support” would be if you wanted to declare e.g. Objectbox models in multiple modules. That’d mean you plan on having several data-layer modules with Objectbox, one for each feature for example?

But it does because of the library. For context, here's how you create an Object box db You declare project dependency, then apply the plugin in the module's build.gradle file. Now to work with Object box, you need an object 'boxStore' which is generated by the builder class MyObjectBox. This class is generated at compile time & will only be generated if there's atleast one @Entity annotated data class in the same module! Now, following clean architecture's abstraction, if all my data entities objects are to be in the domain module, but the MyObjectBox class need an applicationcontext to be passed to build it. So it has to be in the presentation module always. But the presentation module has no @Entity annotated data classes, so this MyObjectBox builder class will not be generated at compile time! Are you getting the point now, that implementation depends on the library itself as well?

Seems to me you make couple of wrong assumptions:

all my data entities objects are to be in the domain module

That’s not accurate, your domain models should be in domain module. Any data entities coupled to libraries specifically must not be in domain module

MyObjectBox class need an applicationcontext to be passed to build it. So it has to be in the presentation module always

Also not accurate,

presentation

should only concern itself with presentation, as its name suggests. Think of it like this: clean architecture promises that e.g. database library is abstracted away in such a way, you could easily swap it at later point. If your domain uses object box models, and your presentation uses objectbox classes, it means objectbox is coupled with all layers of your application and is not swappable at all!