1. CHAPTER FIVE Enterprise Architectures

2. Enterprise Architecture (Introduction) An enterprise-wide plan for managing and implementing corporate data assets Three components Information architecture Infrastructure architecture Application architecture

3. Enterprise Architecture (Illustration)

4. 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

5. 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 http://www- 935.ibm.com/services/us/en/it- services/business- continuity/index.html

6. Disaster Recovery Sites Hot site – ready to go data center Warm site – computer equipment requires configuration Cold site – an empty room Business continuity planning

7. Information Architecture (2) Information security and access policies Manage user access Keep software and patches current

8. Information Architecture (3) Minimize risk by Implementing fault tolerant systems and components RAID Server clusters Maintain off site backups

9. 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

10. Information Architecture (Characteristics) Scalability – Adaptive to growth Reliability – System functions effectively and correctly Performance – System performs according to expected norms

11. Application Architecture The applications used by the organization and the interaction between those applications Two trends in application architecture Web Services Service oriented Architecture

12. Web Services (Introduction) A standardized way of requesting information from heterogeneous computer systems They often encapsulate a business process or group of business processes Make a bank deposit Ship a FedEx package

13. 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

14. Web Services (Illustration)

15. 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

16. 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

17. Software as a Service (SaaS) We subscribe to a software package as a pay-as-you-go service Salesforce.com

18. Platform as a Service We lease a “platform” from a service provider Windows Linux Whatever! www.rackspace.com

19. Virtualization We look at computers as logical units instead of physical units Hardware becomes virtual Providers VMWare** Microsoft Sun And many others

20. Virtualization (Benefits) Better utilization of resources Simplified system administration Reduced power consumption Improved fault tolerance

21. Virtualization (Implementation) A physical machine is partitioned into many logical machines Each virtualized machine is independent of the other A virtualized machine can be easily moved from one physical machine to another Improved security

22. Virtualization (Illustration)

23. 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