Return-Path: X-Original-To: apmail-myfaces-users-archive@www.apache.org Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A8B6C101F0 for ; Sun, 20 Oct 2013 12:35:55 +0000 (UTC) Received: (qmail 14174 invoked by uid 500); 20 Oct 2013 12:35:53 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 13922 invoked by uid 500); 20 Oct 2013 12:35:53 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 13913 invoked by uid 99); 20 Oct 2013 12:35:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Oct 2013 12:35:50 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of smithh032772@gmail.com designates 74.125.82.48 as permitted sender) Received: from [74.125.82.48] (HELO mail-wg0-f48.google.com) (74.125.82.48) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Oct 2013 12:35:42 +0000 Received: by mail-wg0-f48.google.com with SMTP id b13so5446247wgh.15 for ; Sun, 20 Oct 2013 05:35:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=4ubBEFD02BG5A1R3VQWD3eujrtLduIHKV9UbpTts2r0=; b=Ljqus/DkO4QarsrRS3q/0qYtWW6BZkPj/dFmilXe5aXgdvLzDaHZlmX4W/Sih70BXR e8d8kYoYYztdtgy2p/jM4a5lDdemr8Y7Wce6oWz+NbZyGPprRHhcUJ1HMnYv/HL9Gdpq Mve0jrY9zPTcqtqLGQ1F4iE5TqECE7dvQwLhOauFUu5nK9DuxcCZE1VE8/V/oPxFgY4o xiZAoXWyxqOFKReMWTky+yz8rC9RCypbmiutmBOu+ul9ihNxSFM0tVCBiYSoXwvRO60R 7Tb+gAfS+D1g3F0b4/Zj85VgMXU6krH2lvoJOXtzzOF58lDiQPmq7JPiXaoAwu6dbB+p Txwg== MIME-Version: 1.0 X-Received: by 10.194.201.225 with SMTP id kd1mr1211673wjc.35.1382272522558; Sun, 20 Oct 2013 05:35:22 -0700 (PDT) Received: by 10.227.208.7 with HTTP; Sun, 20 Oct 2013 05:35:22 -0700 (PDT) In-Reply-To: <1382271473.16319.YahooMailNeo@web28905.mail.ir2.yahoo.com> References: <1382271473.16319.YahooMailNeo@web28905.mail.ir2.yahoo.com> Date: Sun, 20 Oct 2013 08:35:22 -0400 Message-ID: Subject: Re: [OT but still JSF]: Clustering, session replication, and database, too From: "Howard W. Smith, Jr." To: MyFaces Discussion , Mark Struberg Content-Type: multipart/alternative; boundary=047d7b86f172b0a29804e92b66a2 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b86f172b0a29804e92b66a2 Content-Type: text/plain; charset=ISO-8859-1 On Sun, Oct 20, 2013 at 8:17 AM, Mark Struberg wrote: > This can also be very helpful to 'scale out' in case you need performance: > > All write stuff is only performed on the master node, but expensive > queries/searches might be performed on the n replication nodes. Of course > this needs a special handling in your app, but allows to move the expensive > queries away from your primary node. > hmmm, had a question or two, or seeking clarification (or a bit more details or even a reference to a blog/article/document). 1. scale-out usually mean different physical servers? scaling out multiple databases on one physical server, usually (or I would assume) means that the hard drive becomes the bottleneck, if hard drive contain multiple databases. right? 2. hmmm, had another question, if I remember it, then I can ask it later. --047d7b86f172b0a29804e92b66a2--