Eight Pillars of an Enterprise Application Architecture


Published on

Many IT managers find themselves facing escalating enterprise demands for strategic software capabilities at a time when application platforms and other technologies are rapidly evolving and growing more complex. Managing the delivery of business applications is increasingly difficult
even in 'greenfield' situations where most applications are completely new. The job is even tougher in a typical IBM i (System i, iSeries, AS/400) installation where large amounts of legacy code must be modernised and integrated with new applications.

This presentation was delivered to the 'Scoring with Power' conference attendees at the Old Trafford stadium in Manchester on 28th October 2008.

Published in: Technology

Eight Pillars of an Enterprise Application Architecture

  1. 1. The Eight Pillars of an Enterprise Application Architecture <ul><li>Martin Fincham </li></ul><ul><li>General Manager – EMEA </li></ul><ul><li>LANSA </li></ul><ul><li>m [email_address] </li></ul>
  2. 2. It was Simple with System i <ul><li>One server </li></ul><ul><li>One operating system </li></ul><ul><li>One programming language </li></ul><ul><li>One database </li></ul><ul><li>One user interface style </li></ul><ul><li>One synchronous interactive session </li></ul>
  3. 3. So What Changed? <ul><li>New systems are more complex </li></ul><ul><li>End-users have new expectations </li></ul><ul><li>Western labour costs are high </li></ul><ul><li>Technology directions are fluid </li></ul><ul><li>Tight coupling is strangling agility </li></ul><ul><li>Maintenance is crushing innovation </li></ul><ul><li>The Internet presents new security challenges </li></ul>
  4. 4. Demanding more from IT “ The innovative use of IT got us ahead of the competition … but today we are stagnating and our systems are holding us back.” People, process, platform are the fundamental elements of a modern application architecture
  5. 5. We need a Different Approach <ul><li>Technology agnostic </li></ul><ul><li>Centralised meta data </li></ul><ul><li>Single skill set and tooling </li></ul><ul><li>Standards-based interoperability </li></ul><ul><li>Expose functions as services </li></ul>We need someone to give us a complete and proven architecture out-of-the-box again !
  6. 6. What is an Architecture? <ul><li>A software architecture defines how the components of an application are organised </li></ul><ul><li>A ‘blueprint’ defining how applications will service both current and future needs </li></ul><ul><ul><li>Defining how components will be built and implemented </li></ul></ul><ul><ul><li>Defining how parts of an application relate and inter-communicate </li></ul></ul><ul><li>A plan of how an organisation meets their IT objectives </li></ul><ul><li>Examples </li></ul><ul><ul><li>LANSA, Microsoft .NET, J2EE, CORBA, COM, … </li></ul></ul>
  7. 7. The Eight Pillars of a Sound Architecture <ul><li>Is based on a framework </li></ul><ul><li>Provides an application repository </li></ul><ul><li>Provides automation & developer guidance </li></ul><ul><li>Is based on a service oriented architecture </li></ul><ul><li>Supports multiple platforms </li></ul><ul><li>Supports multiple application interfaces </li></ul><ul><li>Integrates legacy applications </li></ul><ul><li>Manages application evolution </li></ul>Source: Paul Conte white paper “ The Eight Pillars of an Enterprise Application Architecture ” published October 2008
  8. 8. From System i to SOA (or whatever you want to call it) 5250 Green Screen Procedural Code Embedded Functions (RPG / COBOL) DB2 Database (integral validation) AS/400, iSeries, System i Components Business Objects Callable Services Any SQL Database (external validation) Windows GUI Rich Web Client Mobile / PDA System i, Microsoft .NET, Linux, Unix Data Services Layer Meta Data Repository Application Server Visual Framework Web Services Interface Today Future
  9. 9. Platform vs. Product