Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think that you have been misled by this question <a href="https://stackoverflow.com/questions/18257335/architecting-webserver-nginx-lighttpd-apache-with-couchbase">Architecting webserver (NginX/Lighttpd/Apache) with couchbase</a> and it's answer. Because you've asked about couchbase and answer was only about loadbalancer.</p> <p>So first of all if you want to build scalable application never use same server for database and application. That could be even virtual machines on one hardware, but don't place webserver and database on one physical/virtual server. Especially if you're planning to use couchbase. Couchbase likes to eat too much iops, so your web server could have insufficient iops.</p> <p>In situation you've described my choise would be to have separate servers for webapp and couchbase. Server pairs webapp-couchbase should be placed near each other (i.e. at least in one datacenter) to minimize latency. You should configure couchbase servers as standalone clusters with XDCR replication (also check what ports are needed to be open for couchbase). Then configure webapp to connect to the nearest server. But in this case you should care about "high availability" by yourself: check <a href="https://stackoverflow.com/questions/18693180/how-to-create-2-nodes-with-backup-but-without-document-balance/">this question</a> to see some advices. If you connect all couchbase servers in one cluster, it will destribute documents around all servers in cluster and even if you connect from web app only to the nearest server, data will be collected from all couchbase servers in cluster.</p> <p>If you'll have some more questions or I should explain something better - just ask in comments and I'll update my answer.</p> <p>UPD: If you're using couchbase >= 2.1.1 you can configure it with <a href="http://docs.couchbase.com/couchbase-manual-2.0/#using-hostnames-with-couchbase-server" rel="nofollow noreferrer">hostnames</a>.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload