Enterprise architecture is regarded as one of the key ways of achieving competitive advantage through information technology. There is a growing demand to reduce costs, increase flexibility, and regulate technology environments.

Enterprise architecture can be conceptually divided into different architectural layers that involve Business Architecture and IT Architecture (Data, Application and Technology Architecture).

Solution architecture then takes a problem, and proposes building blocks to solve it. It often reuses other elements made available by the Enterprise Architecture (Enterprise Building Blocks, Enterprise Capabilities, Architectural standards and guidelines)

Thus, there are a number of different roles & responsibilities of Enterprise Architects working in the Enterprise Architecture team and elsewhere in the organization. However, people may confuse with these roles and responsibilities, for example, an enterprise architect is sometimes confused with solution architect, or technical architect mix up with the role of infrastructure architect. This is because not only their positions sound similar, the responsibilities partially overlap as well. Yet, each role is essential for the success of a project and could not be substituted by another position. Let’s look at their differences more precisely in this article.