Professional Documents
Culture Documents
Adaptive Infrastructure: (Introduction)
Adaptive Infrastructure: (Introduction)
(Introduction)
BH-2002/v1.0/1
Reference:
The Adaptive Enterprise: IT Infrastructure Strategies to Manage Change and Enable Growth
Bruce Robertson and Valentin Sribar Addison Wesley, 2002
BH-2002/v1.0/2
Background
Rise of the Internet and e-Business e-Business can have an impact on every facet of the organization, including processes, applications, staffing, infrastructure, etc. Enterprise borders are starting to disappear. e-Business is all about providing open access to infrastructure services, data, and applications. Rapid technology and business evolution can have impact on enterprise computing infrastructures.
BH-2002/v1.0/3
Background
Business change is occurring at warp speed Business agility
Agility means being prepared for change We must have the infrastructure in place to support change without throwing away everything and starting over each time A completely new start takes too much time and is almost always too expensive.
BH-2002/v1.0/4
Introduction
What is IT infrastructure?
Generally, infrastructure is a relative term meaning the structure beneath a structure. This definition implies different layers of structure, which provide support or services. Your own definitions?
BH-2002/v1.0/5
What is IT Infrastructure?
BH-2002/v1.0/6
What is IT Infrastructure?
Each layer of infrastructure has certain characteristics, including:
Shared by a larger audience than the structure it supports More static and permanent than the structures it supports Considered a service, including the people and processes involved in support, rather than just a physical structure or device Often physically connected to the structure it supports Distinct from the structures it supports in terms of its lifecycle (plan,build, run, change, exit) Distinct from the structures it supports in terms of its ownership and the people who execute the lifecycle
BH-2002/v1.0/7
What is IT Infrastructure?
Your own definitions might be
Anything that is shared across multiple business units, such as ERP, SCM, Email applications Anything that isnt fun anymore!
BH-2002/v1.0/8
Adaptive Infrastructure
An adaptive infrastructure strategy becomes crucial to providing a versatile, flexible, and agile foundation for application deployment. Adaptive infrastructure should exhibit several key traits:
Efficiency. The ability to provide reusable components that are priced reasonably. Effectiveness. The easy integration of all components in a way that supports their robust operation. Agility. Good planning and design processes that allow companies to develop new applications quickly and to repurpose or upgrade their existing infrastructure to support new requirements for existing or new applications.
BH-2002/v1.0/9
BH-2002/v1.0/10
Clash of Cultures
Stability is good
People often feel its good to have an infrastructure that is stable, unchanging, and predictable. Certainly predictable, systematic behavior must be achieved at some level. However, infrastructure must also be flexible, even breakable, to be fully leveraged by business.
What else causes problems in your infrastructure today? Is it technology, processes, or people?
BH-2002/v1.0/12
BH-2002/v1.0/13
Striking a Balance
Adaptive infrastructure strategy must include the people, processes, and technologies that provide ongoing support for an organizations applications.
BH-2002/v1.0/14
BH-2002/v1.0/15
BH-2002/v1.0/16
1. 2. 3. 4. 5. 6.
Identify and Catalogue Technologies Develop Reusable Infrastructure Patterns Develop Adaptive Infrastructure Services Use Good Tools Get Organized Describe Value Through Packaging
BH-2002/v1.0/17
To manage an infrastructure well, we must first identify and catalog all the components by their functional categories. By organizing components into categories, we can assess the complexity of managing hundreds of components. Start to see the components used to deploy applications fitting into different layers of stacked infrastructure.
BH-2002/v1.0/18
BH-2002/v1.0/19
BH-2002/v1.0/20
Pattern-based infrastructures reduce the incredible variety of technologies, processes, and people (skills, roles, etc.) that are required for accurate application delivery, which will result in more focused and repeatable excellence.
BH-2002/v1.0/21
BH-2002/v1.0/22
BH-2002/v1.0/23
Periodic and Annual Processes Having structured, repeatable processes with concrete deliverables will make a difference in terms of the speed, quality, and cost.
o strategic infrastructure planning to review your standard infrastructure patterns and services on a regular annual cycle. o Per-project or tactical infrastructure planning, which is done for each application or new technology being introduced
BH-2002/v1.0/24
BH-2002/v1.0/25
Portfolios
The key is to apply discipline and a set of easy-to-use tools to continuously update your portfolios. Infrastructure portfolios keep you organized as you identify, catalog, and manage your patterns, platforms, and services on an ongoing basis. A portfolio can be something as basic as a physical filing cabinet with folders in it, or a directory structure with word processing documents, spreadsheets, and diagrams. The best way to make a portfolio sharable is to put it on an intranet site using a database or content management system to deliver the information to the widest audience.
BH-2002/v1.0/26
BH-2002/v1.0/27
5. Get Organized
Create new roles and responsibilities, job titles, and even new groups or departments where necessary. Must own the processes of infrastructure planning and development, and make sure that it gets done. Separating the roles allows each group to focus on its particular strengths
Infrastructure Developers Applications Developers
The team can make sure that infrastructure standards, including components, patterns, and services, are in fact available, and more importantly, reused for particular application development projects.
BH-2002/v1.0/28
BH-2002/v1.0/29
BH-2002/v1.0/30
BH-2002/v1.0/31
BH-2002/v1.0/32
BH-2002/v1.0/33
BH-2002/v1.0/34
Pattern-based
Instead of developing infrastructure from the ground up for each new application, businesses can leverage a limited number of reusable infrastructure patterns.
BH-2002/v1.0/35
Pattern-based
The pattern set must be variable enough to cover all major application requirements, but limited in number to deliver the benefits of a simplified environment. Patterns must also provide sufficient detail to enable the design and implementation of high-quality, end-to-end solutions with minimal customization.
BH-2002/v1.0/36
Patterns
Transact Patterns
Support online customer ordering and other applications in which business data is written and stored in a structured database.
BH-2002/v1.0/37
Patterns
Publish Patterns
Support applications with readonly data, such as the online marketing information offered by most companies on their corporate Web sites.
BH-2002/v1.0/38
Patterns
Collaborate patterns
support applications where information (word processing documents, spreadsheets, CAD drawings, etc.) is shared between two or more users. These patterns improve the efficiency of distributed teams that are separated by geographical or corporate boundaries.
BH-2002/v1.0/39
Companies can focus on a limited number of patterns, optimizing the design for each pattern, defining standard products and configurations, and documenting best practices for implementing, managing and scaling those systems. Though the infrastructure patterns are relatively mature, service level requirements will continue to escalate.
BH-2002/v1.0/40