CLUSTER DESIGN CONSIDERATIONS RAM: Memory is a key factor for smooth cluster performance. Couchbase best fits applications that want most of their active dataset in memory. It is very important that all the data you actively use (the working set) lives in memory. CLUSTER DESIGN CONSIDERATIONS memory. When there is not enough memory left, some data is ejected from memory and will only exist on disk. Accessing data from disk is much slower than accessing data in memory. As a result, if ejected data is accessed frequently, cluster performance suffers. Use the formula provided in the next section to verify your configuration, optimize performance, and avoid this situation. • Number of Nodes: Once you know how much memory you need, you must decide whether to have a few large nodes or many small nodes.o Many small nodes: You are distributing I/O across several machines. However, you also have a higher chance

COUCHBASE HIGH-LEVEL ARCHITECTURE  At the highest level, each node in a Couchbase cluster is identical and has two main components: the data manager and the cluster manager. Other important architectural elements are a powerful map reduce engine to incrementally index and query documents, and cross datacenter replication technology to replicate documents across geographical data centers. > CouchBase Architecture Download PDF

COUCHBASE INTRODUCTION – By Srinivas Maddali – Before you leap some Facts on Couchbase Cluster Design considerations > RAM – depending upon the transactions and data accessed > Number of Nodes – If you are able to deploy more nodes you are distributing the IO as also managing Nodefailures become difficult when the are small in number but large nodes and if you have more smaller nodeschances of node failures is great. Keeping these aspects into consideration decisions are to be taken. > Client or server side moxi Couchbase prefers a client-side moxi(a smart client) > Number of Cores – Couchbase is more memory or IO intensive. So 2 core are enough per server/node > Storage Type – SSD reduces IO latency. Random Access of rotating disks can be used > WAN Deployments – Couchbase is NOT intended to have clusters or clients span over DCs. If you requireyou need

COUCHBASE Couchbase Server, originally known as Membase, is an open-source, distributed (shared-nothing architecture) NoSQL document-oriented database that is optimized for interactive applications. These applications must serve many concurrent users by creating, storing, retrieving, aggregating, manipulating and presenting data. In support of these kinds of application needs, Couchbase is designed to provide easy-to-scale key-value or document access with low latency and high sustained throughput. It is designed to be clustered from a single machine to very large-scale deployments spanning many machines. For those familiar with memcached, Couchbase Server provides on-the-wire client protocol compatibility,[2] but is designed to add disk persistence, data replication, live cluster reconfiguration, rebalancing and multitenancy with data partitioning. In the parlance of Eric Brewer’s CAP theorem, Couchbase is a CP type system meaning it provides consistency and partition tolerance.

COUCHBASE02 – By Srinivas Maddali – Before you start exploring this section you need to have… Resource RequirementsThe following hardware requirements are recommended for installation:01. Quad-core for key-value store, 64-bit CPU running at 3GHz02. Six cores if you use XDCR and views.03. 16GB RAM (physical)04. Block-based storage device (hard disk, SSD, EBS, iSCSI).05. Network filesystems (e.g. CIFS, NFS) are not supported. A minimum specification machine should have the following characteristics: 01. Dual-core CPU running at 2GHz for key-value store02. 4GB RAM (physical) > Download PDF For Full Information