Keep the client experience easy - single server contact point
Your company will have one or two web servers ... and you'll be visited by one or two million different clients. So it makes logical sense for all the complicated stuff to go on your one or two machines, and leave your clients with just a simple browser.
Have you even got on the phone ... to a utility, or travel company, or government office, or insurer or bank ... and found that you're referred on from one person to the next, to another and then to a fourth - who puts you on hold or tells you to call in again on another number? I have, and it makes sense - if you possibly can - when you're providing a service to provide a single point of contact. Not only to improve the experience of your customer, but also to make efficient use of you own resources.
Putting these thoughts together, it's logical to have a single web server program - such as Apache httpd - running on a server computer as the single point of contact for your organisation or web application. Then have that server, "silently" as far as the visitor is concerned - run scripts in Perl or PHP, which it turn refer on to databases using MySQL or some other technology - (Apache + Mysql + Perl / PHP = AMP). And then - with all this open source - what better operating system to oversee the whole than Linux, and you have your LAMP application.
There is a lot to deploying LAMP - but far better that than having to configure lots of machines and services or make life complex for your users. And you can learn just how the elements on the diagram that I've used to illustrate this article go together on our deploying LAMP training course (written 2008-03-27, updated 2008-03-28)
Associated topics are indexed as below, or enter http://melksh.am/nnnn for individual articlesA601 - Web Application Deployment - Apache httpd - an overview 
Apache httpd - a robust, open source web server - (2013-04-16) 
An FAQ on the Apache httpd and Apache Tomcat web servers, and on using them together - (2009-05-17) 
Why put Apache httpd in front of Apache Tomcat - (2009-03-12) 
Internal Dummy Connections on Apache httpd - (2009-03-02) 
Tuning httpd / the supermarket checkout comparison - (2009-02-26) 
Sticky Sessions with mod_jk (httpd to Tomcat) - (2009-02-12) 
Apache httpd and Apache Tomcat miscellany - (2009-01-30) 
Keeping on an even keel - (2008-11-21) 
Apache, Tomcat, Jakarta, httpd, web server - what are they? - (2007-07-13) 
The LAMP Cookbook - Linux, Apache, MySQL, PHP / Perl - (2006-11-13) 
Web Application Components - (2006-03-28) 
Why run two different web servers - (2006-01-25)
Some other Articles
Comparing hotels - as a guest and from the proprietors viewSelling curry to the chinese takeawayFirst Great Western WeekendPlease support improvements in our train serviceKeep the client experience easy - single server contact pointSetting up a new user - Linux or UnixEaster Sunday at 404, The SpaAll Change, Portsmouth HarbourDynamic Memory Allocation in C - calloc, reallocString interpretation in Ruby
4206 posts, page by page
Link to page ... 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85 at 50 posts per page
This is a page archived from The Horse's Mouth at
the diary and writings of Graham Ellis.
Every attempt was made to provide current information at the time the
page was written, but things do move forward in our business - new software
releases, price changes, new techniques. Please check back via
our main site for current courses,
prices, versions, etc - any mention of a price in "The Horse's Mouth"
cannot be taken as an offer to supply at that price.
Link to Ezine home page (for reading).
Link to Blogging home page (to add comments).