Is NIA follow the full recommend app modularization from google especially in data layer and it's dependencies ?

[Abdelsattar]

I was reviewing the latest documentation from Google on modularization and noticed that the data layer is quite different in NIA, as illustrated in the following image from NIA:

The Data Module includes all the repositories and was not split into standalone modules for :data: topic, :data:user, etc.

As I would expect to see from Google flow

Also, does it make sense to split each data into different modules like Google Docs, or should we keep them all in one module?

[AndresMaca]

fwiw i have seen the pattern :data: topic, :data:user quite often in the industry. I think that having one big :data module have some big disadvantages. Specially from arch, recompilation and collaboration point of view. I had exactly the same question a couple of weeks ago.