In the fifth part of this series, we explore the guiding principles behind undertaking an ADO deployment, including optimizing where optimal, knowing what kinds of change you can affect, and coordinating deployment and management appropriately and effectively.

Principle 1: Optimize where optimal

Given all of the technological and delivery options available, the first principle of making an application delivery optimization (ADO) acquisition is to optimize where optimal. IT can architect or intervene to improve delivery in at least five major areas. Here's how:

Application development: This is not part of ADO proper, but the architecture and implementation of applications play a vital role in defining the parameters for application performance because this is where many performance problems are born. For example, client-server communications can be frequent or infrequent, terse or "wordy" and can use highly