You wouldn't choose to use a Ford Ka as your car for that holiday of a lifetime travelling across Europe, neither would you choose a Jaguar as your idea car for the school run. Yet both of them are perfectly good models of car. Indeed as a family, you might have one of each.

Apache httpd and Apache Tomcat and both web servers. You can have either of them listen on port 80 for requests in http and answer those requests. But just as the luxury Ford - the Jaguar - was great for that holiday and the budget Ford - the Ka - was great for the school trips, so each has its own use and place.

Apache httpd - the original Apache Web Server is sometimes just called "Apache" still. It's great for serving out static content - HTML pages that don't change, Images, style sheet, and also shorter scripts and quieter site activities with the scripts often written in Perl or PHP. Apache httpd is pretty common - I think I've seen comment that it's the server that fronts as many as 70% of all registered domains worldwide.

Apache Tomcat is a different beast. Rather than serving each page "ad hoc" as it's called up, it runs web applications in containers and it keeps them running, handling requests from multiple users, with the application staying in the computer memory. In contrast to httpd, Tomcat is great for the big sites - on line banking and passport applications, shopping sites for huge supermarkets, end the like.

Just as a family might have a Ka and a Jag, so a web site might be run with both httpd and Tomcat. In fact, it would be much more common that having two cars as both servers are open source and only cost you memory and resources. It's usual for httpd to be the user-facing server since so many requests made are for odd images, help information, style sheets and the like. Then httpd calls on to Tomcat in the case of meatier requests. Properly configured, the user doesn't even need to know that the web server he's contacted has passed his request on and is just acting as a relay station.

Links:
Course - Deploying Apache httpd and Tomcat
Connection Apache httpd to Tomcat - 7 ways to do it
(written 2006-01-25 15:26:20)

Commentator	says ...
Kelly:	You have described half the Apache implementations I've worked on. I only have http at home, but work uses whatever is appropriate. I agree with your analogy. Kelly (comment added 2006-01-25 16:52:21)

A657 - Web Application Deployment - Using httpd to front Tomcat
A099 - Java Application - Deployment on the Web
A655 - Web Application Deployment - Using Tomcat and Apache httpd Together
A601 - Web Application Deployment - Apache httpd - an overview
A651 - Web Application Deployment - Tomcat Overview

Back to Eating for the single business traveller

Previous and next or Horse's mouth home

Forward to Learning to program in Perl or PHP

What to do with milk
Short Linux and Perl courses for small groups
Woman screaming at me
Learning to program in Perl or PHP
Why run two different web servers
Eating for the single business traveller
PHP - dividing a string up into pieces
Giving an excuse for Christmas
Giving the researcher power over database analysis
Well House Manor
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 at 50 posts per page


This is a page archived from The Horse's Mouth at http://www.wellho.net/horse/ - 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).