Oracle Architecture and Design Issues for E-Busine

[ahmadbilal]

<b>Capacity Planning, Architecture, and Design Issues Essentials</b>
Proper capacity planning can minimize performance problems in the system after it is implemented.

Capacity planning for an e-Business is an art rather than a science because its requirements change all the time.

Oracle8i (release 8.1.6) and higher provide a mechanism called the STATSPACK utility for historical data collection and the capability to translate the data into reports that can show database usage trends.

One key characteristic of a successful e-Business is its capability and willingness to change quickly according to market needs. An even better characteristic is its capability to predict the direction in which the market might shift in the future so that it can prepare in advance to meet the new demands.

The e-Business architecture is better than a straight client/server architecture because the client doesn't stay connected to the database, the application server stays connected only for the time required to make a request and receive the results back from the database server, network traffic is reduced, idle processes do not consume resources, and response time is improved.

When you start to move your systems to an e-Business, it can help to start small and identify a small project that can quickly make the transition and at the same time provide high impact and return on investment (ROI). When this transition is successful, you can build on the experience and feedback from this venture.

An e-Business needs to have a forward-looking application architecture that deals with the following critical requirements:





http://www.informit.com/articles/articl ... 25146&rl=1