Thin
Client
|
Thick
Client
|
Mostly
it is a web based client. Will be accessed through a common client called
browser
|
It
will be accessible through client software which is installed locally
|
Business
logic will be there in middleware’s or application servers.
|
Business
logic will be installed in the local machine.
|
When
the URL is accessed most of the business logic will be executed on the
server. And some client side processing and rendering happens within the
browser.
|
When
the client get installed all the business logic of the application installed
locally
|
Thin
client uses stateless connections. For each request connection will be opened
and after the response it will be closed
|
Thick
client uses dedicated connections
|
Thin
clients are slower in response
•
Connection needs to be opened explicitly for each request
• Pages needs to be downloaded from presentation layer • Data needs to be retrieved from the DB • Business logic related processing will be happening in the middle wares or application servers |
Thick
clients are faster in response
•
most of the processing happens locally
• Connections will be closed only explicit logouts |
Thin
clients will be used by the external users. Ex: Bank customers
|
Thick
clients will be used by the internal users most of the times: Ex: Bank
employees and customer support executives
|
My intention to launch this blog is for the beginners who can learn basics of performance testing and fundamentals in Loadrunner tool. This blog will be a quick learner to the newcomers once reading the articles posted in my blog. Hoping you all like my blog. I am happy to welcome your suggestions and ideas.
Thursday, 11 August 2016
Thin Client Vs Thick Client
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment