Who Needs an Architect?

The text makes some analogies of a software engineer and an architect. First, it begins talking about the architects. Then, it starts to talk about the relation between architecture and software. Some of the ideas that author come up with are that software architects are engineers with a wide expertise. These engineers usually have a better understand of the environment and how the system should behave. One important point is that architects must detect the important things and components about the system. The software architect is the one that is going to design the solution, that’s why he should be the most experimented engineer in the team. Moreover, as the expert of the team, if the architect say that something is important, it is important.

In my experience, I am agreed with the author, the software architect must be the most experimented engineer of the group, and everyone should follow his guide. In my work team, I have a software architect, and he is responsible for designing the software solutions. I think that especially nowadays where microservices are in its boom is very important that a team have at least one software architect. For example, where I work, we use the Amazon Web Services suite to develop and deploy our services, especially lambdas and API Gateway. Therefore, the software architect has an Amazon Web Services certification, and he is the one that has the overall view of the solution, so that he can purpose new architectures taking advantage of all the power of Amazon Web Services.

I think that as I said in another post, the architecture is a very important thing in nowadays software projects. And obviously, in order to have a good architecture, it is needed to have a good architect. The reading was very interesting, I really enjoyed it.