|
Code base and data are usually shared in several ways for 3-Tier applications.
Each sharing option has subsequent business, technology and legal implications.
Enterprise Option Each application has
logically independent presentation layer, business logical layer and database schema.
This is an architectural option for applications which do not interact with each other.
And it's likely that applications have very different business requirements. The reusability
among applications are limited to the base framework API and some utility classes.
Network Option All applications share the same
presentation layer, business logical layer and database schema. This is a good option
for applications which are very similar or almost identical. The danger of using this
option is that those similar or identical applications may evolve into somewhat different
application. The initial cost of implementation is higher than 2 other options since it
requires some configuration functionality for managing admin layer applications.
Hybrid Option Applications share one or two of
three layers. This is a choice for applications which share some basic functionality
and yet differ in some other behaviors. The initial cost of implementation is lower
than network option, but higher than enterprise option. than 2 other options since it
requires some configuration functionality for managing admin layer applications.
Related Topics
3 Tier Architecture for Web Applications
3 Tiers of Business Applications
Benefits of Component Development, Characterestics of Business Component and Common Business Components
|