This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
First im finding it hard to find out the appropriate forum to put this question on Javaranch, so please feel free to move to forum you think would be suitable for this question,
We have a physical two tier application which is logically layered which means that we have divided our code into several layers so that we can port the application to physical three tier architecture.
Now the thing im looking is that is there any benchmark/whitepaper which lists the benefits in quantitative terms for moving an computational intensive two tier architecture application to three tier architecture application.
I think it will be application specific, but im still hopeing that there should be some information/numbers in general about benefits of moving two tier application to three tier application.
If its green its biology if its stinkks its chemistry if it has numbers it is Maths and if it doesn't work its TECHNOLOGY
is there any benchmark/whitepaper which lists the benefits in quantitative terms for moving an computational intensive two tier architecture application to three tier architecture application.
I suspect the advantages would depend entirely on details of the application. The obvious point being that intensive computation can be carried out on multiple back-end machines managed by your middle tier. The tradeoff involves extra communication delays - object serialization, etc versus the time spent in actual computation.
Give us a hint - how much time does one "job" take - seconds, minutes, hours, days???