After discussing about Application Architecture and the future trends in this architectural layer, now lets talk about enterprise application integration. I have been mentioning application architect in my previous posts as well, and I will try to involve the Application Architect in this post as well.
Enterprise Application Integration is a very new concept. I think of it as a mix and match activity, where as an organization you hash out the various components you need to make your application architectural layer, and then shop for those in the outside world. Essentially rather than reinventing, utilizing the resources from vendors, and then molding them to best work with your organization.
While this sounds exciting, a lot of work is done behind the curtain to create such type of solutions.
As an architect working with the concept of EAI (Enterprise Application Integration), he/she needs to keep some things in mind;
Lets shift our focus and talk about application architect , role and why they are essential to an organization.Referencing the Gartner article; https://www.gartner.com/doc/2407415/defining-roles-responsibilities-application-architect and another blog https://www.future-processing.pl/blog/role-of-the-application-architect/
Application architect comes after Enterprise Architect, and systems architect. They are also known as Software Architect as they are very close to the development/ IT layer. Since the application architect is very close to the technology layer, he/she has a better understanding of the applications and their dependencies within the organization, and they are able to better work on guiding the organization towards a more robust and an efficient application architectural layer.
Enterprise Application Integration is a very new concept. I think of it as a mix and match activity, where as an organization you hash out the various components you need to make your application architectural layer, and then shop for those in the outside world. Essentially rather than reinventing, utilizing the resources from vendors, and then molding them to best work with your organization.
While this sounds exciting, a lot of work is done behind the curtain to create such type of solutions.
As an architect working with the concept of EAI (Enterprise Application Integration), he/she needs to keep some things in mind;
- what is the goal/ objective of this activity?
- what type of solution are we looking at?
- assessing the internal organization, and then researching external market for options?
- what will be the return on investment (ROI). Would this be cheaper or an internal engineering might be cheaper for us?
- Once the goals are hashed, the architect needs to start matching these goals with the vendor applications. Are the applications flexible and easy to be maintained?
- what will be the knowledge curve once installed within my enterprise?
- short term versus long term advantage of this solution?
- Custom Point to point integration
- On Premises Integration Platforms
- iPaaS
- Integration brokerage
Lets shift our focus and talk about application architect , role and why they are essential to an organization.Referencing the Gartner article; https://www.gartner.com/doc/2407415/defining-roles-responsibilities-application-architect and another blog https://www.future-processing.pl/blog/role-of-the-application-architect/
Application architect comes after Enterprise Architect, and systems architect. They are also known as Software Architect as they are very close to the development/ IT layer. Since the application architect is very close to the technology layer, he/she has a better understanding of the applications and their dependencies within the organization, and they are able to better work on guiding the organization towards a more robust and an efficient application architectural layer.
 |
| Different architect roles |
No comments:
Post a Comment