Connectors cover many non functional requirement attributes which like you point out de risk the project. Components and their behaviors is where the functiona

Connectors cover many non functional requirement attributes which like you point out de risk the project. Components and their behaviors is where the functional requirements are and also many non functional requirements are handled. There is tons of architecture and design space when it comes to e.g. the SOLID patterns (applied to components not objects) and the onion architecture comes into play. So there is tons of interesting stuff to do with components. About derisking: the core pillar of architecture when it comes to Microservices is finding the right bounded context. This massively de-risk projects as well. It is not so much technical architecture like the mentioned connectors but analysis of the requirements. Architecture on that level is very interesting.