1. Enterprise Architectures
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

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
Capacity planning
Reliability – System functions effectively and correctly
Performance – System performs according to expected norms
Usability

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

12. Grid Computing (Introduction)
Grid computing distributes resources (hardware / networking / storage / etc…) geographically
It’s typically uses many computers to solve a problem

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. Open Systems
A trend is toward open systems instead of proprietary systems
Linux
MySQL
Anyone can modify the source code of an open system

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

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

17. Platform as a Service We lease a “platform” from a service provider
Windows
Linux
Whatever!