January 31, 2016 / Dennis Holinka
Topic 2 – Application Architecture layer
This week's posts go over the Application Architecture layer, the various perspectives, and related reflections in the blog.
Post 2 - Enterprise Application Integration
Enterprise Application Integration has been around for almost 10 years but the advent of a new architectural paradigm has supercharged and revitalized the comeback of EAI for application architecture. Gartner expects a paradigm shift into a new architecture it terms the Nexus of Forces. The nexus of forces combines cloud, social, mobile, and data together to form the new foundation of a modern application architecture. The view is that application architecture founded upon the use of service oriented architecture (SOA) using web oriented architecture (WOA) protocol approaches (e.g. REST) will form the backbone of the new architecture. The architecture will utilize micro-services as has been demonstrated by Amazon and Netflix to allow for the ability of application to achieve extreme scale by way of elasticity.
This will have an impact on the way applications are integrated internally but also external to the company. Many services will be provided and be made available by integrating cloud services which will commoditize many of the existing internal services. The application architecture will have to be flexible enough to bind dynamically to external and internal service providers while allowing for the architecture to provide dynamically generated data inputs needed by the cloud provider. Mobility will be affected by the cloud but not in integrating services from internal to external cloud providers but rather at the EAI center of the mobility universe - at the app-store level. In other words, apps will need to integrate and invoke other apps that are installed and trusted by the mobile user on the mobile device. This will call for a UI client integration mechanism that will allow for a discovery based integration binding logic between apps while allowing the application to provide data inputs dynamically to the invoked app by way of negotiated invocation integration parameters. No matter what the integration mechanism is, we know that the 3 / n Tier application architecture will not be satisfactory for the nexus of forces architecture. Last, the application architecture will require an event based architecture that will allow for events to be subscribed and published which will allow for dynamic integrations between applications and into data services streams and events. The events and data streams from social and other transactions will make up the nexus. All of these new patterns will have to architected and blueprinted for reuse by solution architects throughout the enterprise.
Enterprise Application Integration has been around for almost 10 years but the advent of a new architectural paradigm has supercharged and revitalized the comeback of EAI for application architecture. Gartner expects a paradigm shift into a new architecture it terms the Nexus of Forces. The nexus of forces combines cloud, social, mobile, and data together to form the new foundation of a modern application architecture. The view is that application architecture founded upon the use of service oriented architecture (SOA) using web oriented architecture (WOA) protocol approaches (e.g. REST) will form the backbone of the new architecture. The architecture will utilize micro-services as has been demonstrated by Amazon and Netflix to allow for the ability of application to achieve extreme scale by way of elasticity.
Figure: Nexus of Forces on Application Architecture and Cloud First Unified Ecosystem
This will have an impact on the way applications are integrated internally but also external to the company. Many services will be provided and be made available by integrating cloud services which will commoditize many of the existing internal services. The application architecture will have to be flexible enough to bind dynamically to external and internal service providers while allowing for the architecture to provide dynamically generated data inputs needed by the cloud provider. Mobility will be affected by the cloud but not in integrating services from internal to external cloud providers but rather at the EAI center of the mobility universe - at the app-store level. In other words, apps will need to integrate and invoke other apps that are installed and trusted by the mobile user on the mobile device. This will call for a UI client integration mechanism that will allow for a discovery based integration binding logic between apps while allowing the application to provide data inputs dynamically to the invoked app by way of negotiated invocation integration parameters. No matter what the integration mechanism is, we know that the 3 / n Tier application architecture will not be satisfactory for the nexus of forces architecture. Last, the application architecture will require an event based architecture that will allow for events to be subscribed and published which will allow for dynamic integrations between applications and into data services streams and events. The events and data streams from social and other transactions will make up the nexus. All of these new patterns will have to architected and blueprinted for reuse by solution architects throughout the enterprise.
Figure: Event Driven Architecture of the Nexus of Forces
No comments:
Post a Comment