john e skrev den 08-08-2008 16:33:
Richard wrote:

The point of this whole comment. Don't shy away from .Net or Java
technologies because you may have a two server environment. Most of the
time the web server simply runs the web code, but the database still
stays on the "i". Not a bad tradeoff since a web apps code is usually a
few megs. It's all about the database !!

One the advantages of having an as/400 is that you only need one box. This box runs the application and the database. It's also very scalable, this one box, and it can support 1000's of users.

If you split the app server and the db server into two boxes then you have a bottleneck, i.e. the communication of data between these two boxes. So you have to take this into account when designing your application. And if you have lots of users you maybe have to put another windows web application into the mix. Making it all complicated and difficult to manage. Windows is not powerful enough to support a database and application server on one box. The as/400 is designed for this. There is no I/O bottleneck between the applications and the db.
I am afraid that the "Windows is not powerful enough for a database and application server" statement doesn't hold (anymore :) ). I've seen a four-CPU Windows box service a very busy (+1200 simultaneous web users) web application with a MySQL database which had plenty of muscle to spare.

My laptop can do an API call in Java to our AS/400 and get a response back over a 100 Mbit network in about 1 ms. That is faster than I can do the same from Java on the AS/400 itself.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].