About Java Database architecture

Question

0.00/5 (No votes)

See more:

hello friends.
is that not possible that if we use 3^rd tire architecture will take more time to execute then 2^nd tire architecture? Because the Bigness Logic and Database are at the different System. So Why Should we have top use it...?

Posted 17-Feb-15 17:34pm

Ankit Torino (Dom)

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Accepted Answer · 2015-02-17T17:58:00

The reason to use 3 tier architecture is typically not the performance, at least not the only reason. The benefits lie elsewhere. Have a look at for example
- Multitier architecture[^]
- N-Tier Architecture and Tips[^]

Regarding your comment on business logic and database residing on different systems, this is often true also in 2 tier applications. Having this said, the speed of executing the database commands can be the same in both architectures. The overall execution time from end to end may be different but again this probably wouldn't be the reason to use or abandon n-tier architecture. Cosider for example that if the application and the database originally resided on the same computer the performance may get better if they are separated into different tiers, especially in a situation where they both are consuming heavily a bottleneck resource such as CPU or disk