PUBLIC MARKS from holyver with tag "load balancing"

in this article, i outline a step-by-step process for incrementally scaling your deployment, from a simple single-node drupal install running all components of the system, all the way to a load balanced, multi node system with database level optimization and clustering. since you almost certainly don't want to jump straight from your single node system to the mother of all redundant clustered systems in one step, i've broken this down into 5 incremental steps, each one building on the last. each step along the way is a perfectly viable deployment.

Improving Drupal's Performance with the Boost Module for the UN's Millennium Campaign. How the Boost Module Helped a Very High Traffic Drupal Site Stay Online

Lors de la mise en production d'une application Internet ou intranet, il est fréquent de vouloir protéger les transferts par une connexion sécurisée (HTTPS). Même si Tomcat le permet (il suffit d'activer une option dans le server.xml de Tomcat), utiliser Apache est un meilleur choix du fait de sa vitesse. De plus l'utilisation d'Apache permet de se débarrasser des :8080 et autres numéros de ports dans l'url, du fameux " /MonApp " à la fin de la dite url et enfin la possibilité il offre une intégration plus aisée dans un environnement avec charge répartie (Load Balancing).

This tutorial shows how to configure a MySQL 5 cluster with three nodes: two storage nodes and one management node. This cluster is load-balanced by a high-availability load balancer that in fact has two nodes that use the Ultra Monkey package which provides heartbeat (for checking if the other node is still alive) and ldirectord (to split up the requests to the nodes of the MySQL cluster).

In this tutorial I will describe how to set up a highly available NFS server that can be used as storage solution for other high-availability services like, for example, a cluster of web servers that are being loadbalanced. If you have a web server cluster with two or more nodes that serve the same web site(s), than these nodes must access the same pool of data so that every node serves the same data, no matter if the loadbalancer directs the user to node 1 or node n. This can be achieved with an NFS share on an NFS server that all web server nodes (the NFS clients) can access.

Web tier clustering is an important part of J2EE scalability and high availability. Traditionally, load balancing is done via front end load balancer (either software- or hardware-based) while the session replication (for fail-over) is done by the web container. Here we have done a benchmark study of http session replication using JBoss Application Server (AS). We also compare JBoss performance against the Tomcat standalone. Please note that JBoss web container also uses embedded Tomcat in non-clustered mode. They differ only in the clustering solution module. For details of both implementation, please refer to both the JBoss and Tomcat documentation. The HttpSession replication performance comparisons are based on JBoss AS 4.0.3SP1 (with JBossCache 1.2.4 and JGroups 2.2.9). Previously, we have published results based on JBoss AS 4.0.2 (August 2005). But the current version has been found to provide dramatic performance improvement.

Clustering allows us to run an applications on several parallel servers (a.k.a cluster nodes). The load is distributed across different servers, and even if any of the servers fails, the application is still accessible via other cluster nodes. Clustering is crucial for scalable enterprise applications, as you can improve performance by simply adding more nodes to the cluster. The JBoss Application Server (AS) comes with clustering support out of the box. The simplest way to start a JBoss server cluster is to start several JBoss instances on the same local network, using the run -c all command for each instance. Those server instances, all started in the all configuration, detect each other and automatically form a cluster. In the first section of this chapter, I discuss basic concepts behind JBoss's clustering services. It is important that you understand those concepts before reading the rest of the chapter. Clustering configurations for specific types of applications are covered after this section.

Lors de la mise en production d'une application Internet ou intranet, il est fréquent de vouloir protéger les transferts par une connexion sécurisée (HTTPS). Même si Tomcat le permet (il suffit d'activer une option dans le server.xml de Tomcat), utiliser Apache est un meilleur choix du fait de sa vitesse. De plus l'utilisation d'Apache permet de se débarrasser des :8080 et autres numéros de ports dans l'url, du fameux " /MonApp " à la fin de la dite url et enfin la possibilité il offre une intégration plus aisée dans un environnement avec charge répartie (Load Balancing).

The latest version of the Tomcat servlet container provides clustering and load balancing capabilities that are essential for deploying scalable and robust web applications. The first part of this article provides an overview of installation, configuration, usage, and extension of clustering and load balancing features. The second will introduce a sample web application to demonstrate the steps involved in configuring Tomcat server instances to enable clustering, and will study session persistence using in-memory replication in the cluster environment.