Günay's Coding World

TomCat : Tomcat, is an open-source web server developed by the Apache Software Foundation (ASF). Tomcat implements several Java EE specifications including Java Servlet, JavaServer Pages (JSP), Java EL, and WebSocket, and provides a "pure Java" HTTP web server environment for Java code to run in. MongoDB : MongoDB is a cross-platform document-oriented database. Classified as a NoSQL database, MongoDB eschews the traditional table-based relational database structure in favor of JSON-like documents with dynamic schemas (MongoDB calls the format BSON), making the integration of data in certain types of applications easier and faster. Released under a combination of the GNU Affero General Public License and the Apache License, MongoDB is free and open-source software. MySQL : MySQL is a popular choice of database for use in web applications, and is a central component of the widely used LAMP open source web application software stack (and other "AMP" stacks)...

Start Apache and Tomcat Start Apache: $APACHE_HOME / bin / apachectl -k start To stop use: $APACHE_HOME / bin / apachectl -k stop Start Tomcat: $TOMCAT_HOME / bin / startup.sh Stop Tomcat: $TOMCAT_HOME / bin / shutdown.sh

There are pretty much two ways to set up basic clustering, which use two different Apache modules. The architecture for both, is the same. Apache sits in front of the Tomcat nodes and acts as a load balancer. Traffic is passed between Apache and Tomcat(s) using the binary AJP 1.3 protocol. The two modules are mod_jk and mod_proxy . mod_jk stands for “ jakarta ” the original project under which Tomcat was developed. It is the older way of setting this up, but still has some advantages. mod_proxy is a newer and more generic way of setting this up. The rest of this guide will focus on mod_proxy , since it ships “out of the box” with newer versions of Apache. You should be able to follow this guide by downloading Apache and Tomcat default distributions and following the steps. Clustering Background You can cluster at the request or session level. Request level means that each request may go to a different node – this is the ideal since the traffic would be balanced across...