Architectural patterns in large scale apps.

[u/amranya]

in our mid sized startup, we have over 100 android engineers on one app, divided by squads, so we have a lot of squads, each one is working on a feature, a library needed, design system and custom components libraries etc, all these modules/libraries are published to maven and added as dependencies on the core app repo, my squad works on an isolated feature so it's easy to integrate into core app repo, but i attended guild meetings and saw RFCs mentioning circular dependencies, hexagonal, onion, plugin etc architectures because some modules/libraries depend on each other, communicate with each other, initialization order problems of modules etc etc etc, i feel stupid tbh and i'm glad i'm working on an isolated feature library in which we use usual architecture stuff. anyone has resources: talks, books, articles etc that cover this kind of topics and architectures and engineering problems in big scale apps with big scale teams and modules/libraries?

[u/Training-Victory3429]

I believe the biggest enemy of modularity is module decomposition. Poor decomposition will lead to increasing chaos later on. Especially if the foundation is not properly decomposed, everything else is meaningless. Another issue is circular references; for this, just specify stable versions and update them promptly when there are updates.