Why did you choose Apache/MySQL/PHP for the web server and Java for the scheduler?
The criteria we used for selecting our development environment were: platform independence, speed, power, acceptance level, and free availability. The Apache/MySQL/PHP combination provides a platform-independent solution that is very fast and provides the power we need to do some complex server-side scripting. The combination is available for free and has reached a high level of acceptance, so much so that Red Hat is distributing it bundled with its Linux 7.0 release. PHP was not appropriate for the scheduler (partly because the scheduler does not necessarily run on the same machine as the web server), so we used Java due to its platform independence and the ease of development that Java provides.
Related Questions
- We have documents stored on Linux, Apache, MySQL and Java/PHP. Is there any way to use the document management software search engine to retrieve these documents?
- We have documents stored on Linux, Apache, MySQL and Java/PHP. Is there any way to use the FileHold search engine to retrieve these documents?
- Why did you choose Apache/MySQL/PHP for the web server and Java for the scheduler?
