Nobody so far has mentioned another factor: as you increase the "distance" (latency) between applications and databases, CPU and memory consumption increases on both sides. I call this phenomenon "proximity effects." These proximity effects can be extremely large in many cases.
I'm also observing more and more organizations finally figuring out that dis-aggregating existing architectures is exactly the wrong direction to head. The management costs and service quality dimunition, in particular, are just not worth it, and they're getting more costly every year. I find I'm getting more and more enthusiastic about not making things more complicated than they need to be, as a general rule -- indeed, to seek opportunities for simplification. And more and more people seem to be coming to the same conclusions nowadays. - - - - - Timothy Sipples IBM Consulting Enterprise Software Architect Based in Tokyo, Serving IBM Japan / Asia-Pacific E-Mail: timothy.sipp...@us.ibm.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
