Enterprise Architectures CHAPTER FIVE Enterprise Architectures
Enterprise Architecture (Introduction) An enterprise-wide plan for managing and implementing corporate data assets Three components Information architecture Infrastructure architecture Application architecture
Enterprise Architecture (Illustration)
Information Architecture (1) Backup and recovery No matter the failure, we cannot loose a transaction We need to recover all data quickly if not immediately Much of this is being done in the cloud But understand the risks
Information Architecture (1a) Disaster recovery and business continuity planning Have a disaster recovery hot (or cold) site available IBM resiliency center http://www-935.ibm.com/services/us/en/it-services/business-continuity/index.html
Disaster Recovery Sites Hot site – ready to go data center Warm site – computer equipment requires configuration Cold site – an empty room Business continuity planning
Information Architecture (2) Information security and access policies Manage user access Keep software and patches current
Information Architecture (3) Minimize risk by Implementing fault tolerant systems and components RAID Server clusters Maintain off site backups
Infrastructure Architecture (Characteristics) Accessibility – what a user has access to Availability – System is available to users (uptime) Flexibility – Adaptive to change Portability – Can move to different devices
Information Architecture (Characteristics) Scalability – Adaptive to growth Capacity planning Reliability – System functions effectively and correctly Performance – System performs according to expected norms Usability
Application Architecture The applications used by the organization and the interaction between those applications Trends in application architecture Grid computing The cloud Service oriented Architecture
Grid Computing (Introduction) Grid computing distributes resources (hardware / networking / storage / etc…) geographically It’s typically uses many computers to solve a problem http://setiathome.ssl.berkeley.edu http://folding.stanford.edu
Web Services (Implementation) Requests and responses are made using a standardized protocol called Simple Object Access Protocol (SOAP) No matter the request the protocol is the same Web services are described using Web Service Description Language (WSDL) All of this is XML
Open Systems A trend is toward open systems instead of proprietary systems Linux MySQL Anyone can modify the source code of an open system www.sourceforge.net
Service Oriented Architecture (Introduction) Encapsulates a repeatable business task or process into a service SOA is an architecture rather than a tool or product you purchase Services are loosely coupled Services can be used individually or joined together Services are typically based on XML and XML-based protocols
Software as a Service (SaaS) We subscribe to a software package as a pay-as-you-go service Salesforce.com
Platform as a Service We lease a “platform” from a service provider Windows Linux Whatever! www.rackspace.com