In recent years the two-tier client/server model was reevaluated and a new
concept built on scalability and maintainability was born: the n-tier
application development paradigm.
Leveraged by Internet popularization and the consequent growth of Web
data-driven applications, the multitier model uses thin, pure, interface
clients, middle-tier business objects installed on application/transaction
servers, and database objects on RDBMS.
The multitier model is definitely more effective: more distributed,
encapsulated, and generic. However, client/server development is very mature,
offering well-known tested technologies, tools, and methodologies that work
closely to produce applications rapidly. The introduction of the n-tier model
delays the application's production line because the programming team must
learn several new technologies and methods to write high-quality ... (more)
When I started using distributed DataWindows, the slow performance frightened
me, usually when the middle server and the client were in separate computers.
At that time I was using a PIII 500 desktop computer, and a PIII 800 database
server over a 10MB network. Although it's not the top-of-the-line hardware
environment, it's still the best some customers can get.
Back then I had resolved to make a few sets of tests, trying to discover the
reasons for performance differences between traditional client/server and the
n-tier application, and possible workarounds. Despite different hea... (more)
In recent years the two-tier client/server model was reevaluated and a new
concept built on scalability and maintainability was born: the n-tier
application development paradigm.
Leveraged by Internet popularization and the consequent growth of Web
data-driven applications, the multitier model uses thin, pure, interface
clients, middle-tier business objects installed on application/transaction
servers, and database objects on RDBMS.
The multitier model is definitely more effective: more distributed,
encapsulated, and generic. However, client/server development is very mature,
o... (more)
When I started using distributed DataWindows, the slow performance frightened
me, usually when the middle server and the client were in separate computers.
At that time I was using a PIII 500 desktop computer, and a PIII 800 database
server over a 10MB network. Although it's not the top-of-the-line hardware
environment, it's still the best some customers can get.
Back then I had resolved to make a few sets of tests, trying to discover the
reasons for performance differences between traditional client/server and the
n-tier application, and possible workarounds. Despite different hea... (more)