Multi-tired Application Vs. Stored Procedures: Top Differences

Tired Applications

The concept of tiered applications presents a solution to design architects that uses distributed resources dynamically with the ability to insert software and hardware when and where they are needed.

Two-tiered client/server applications might require extensive and expensive deployment strategies for DB2 enablers and business logic.

Multi-tiered (three or more tiers) client/server applications greatly reduce the deployment issues because DB2 enablers and business logic are kept on the lower tiers. The client has the presentation layer of the system while the business logic is on the middle tier and the database access on the server tier.

This flexibility comes with many benefits, including:

Each tier can be developed, installed, and maintained independently.

Code from existing business logic and database access can be separated and reused as deemed necessary.

With good planning, you can reuse common software solutions.

Any number of hardware and software configurations can be deployed to produce a modular packaging of information services.

A substantial improvement in the maintenance of client/server applications.

Stored Procedures

Stored procedures reside and execute on the database server (or the server tier), they can be developed and installed with minimal maintenance activity. Stored procedures support and encourage what is, by far, the most pervasive of current computing trends.