Given any problems statement, general tendency for an architect is to start designing based on certain implicit assumptions. These assumptions depend heavily on how the project will be executed among different scrum teams. Architects tend to design a product for a given problem depending upon the team allocation , structure and geo location.
Keeping aside the principle of micro services or decoupled architecture, team structure also plays an important role in shaping of a product. For an example if there are two scrum teams in two different geo location then ultimately modules will be designed differently in an externalized manner by these two teams. If there would have been three scrum teams then somehow, teams will break it further and make total three modules integrated by means of API or well defined RPC.
Remotely located team is more comfortable in developing the module in entirety which does not have any dependency on other team until the development sprint is complete. This is not good nor a bad practice but it is the conscious or unconscious factor which attributes to the design of a system by an architect.
Originally published at https://justvikas.com on May 30, 2020.