Not arguing about that 😁 But the way there was something like 6 layer architecture, ~100 different sub-domains + technical modules and the "grid" projected to Maven modules 🤷‍♂️ (that's only 600 modules, I know, but that's how it came along 😁)

To me using the build tool for this more falls into the "if you only have a hammer..." category 🤷‍♂️

Honestly, I'm not convinced of this. A first class citizen like JPMS, yes. But I'm not convinced to couple build tool and architecture. I've worked in a project for quite a while that followed this approach and had over 700 Maven modules. Just building the reactor took over a min

After 12 years at @tngtech, this week I'm starting my new job as principal software architect at @tado. I'm super thrilled to help with tackling a continuous exponential growth of connected devices and contribute to support renewable energy 🥳

😊

Always so happy when I hear people liking it or getting benefit from it 😊

0. 😬👴

Yes, I also think so. But AFAIK if you use the test infrastructure for integration tests it will spin up only the contexts for the module and it's dependencies. So, you'll at least see that the Spring contexts work like this on the test level.

Isn't that close to the Spring Modulith approach? spring.io/blog/2022/10/21/in…