Couchbase Server

Couchbase Server, originally known as Membase, is an open-source, distributed (shared-nothing architecture) multi-model NoSQL document-oriented database software package that is optimized for interactive applications. These applications may serve many concurrent users by creating, storing, retrieving, aggregating, manipulating and presenting data. In support of these kinds of application needs, Couchbase Server is designed to provide easy-to-scale key-value or JSON 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.

Couchbase Server
Developer(s)Couchbase, Inc.
Initial releaseAugust 2010 (2010-08)
Stable release
6.6.0 / August 12, 2020 (2020-08-12)
Written inC++, Erlang, C,[1] Go
TypeMulti-model database, distributed key-value database, document-oriented database
LicenseApache License 2.0, freemium
Websitecouchbase.com
Couchbase at AWS Summit

Couchbase Server provided client protocol compatibility with memcached,[2] but added disk persistence, data replication, live cluster reconfiguration, rebalancing and multitenancy with data partitioning.

Product history

Membase was developed by several leaders of the memcached project, who had founded a company, NorthScale, to develop a key-value store with the simplicity, speed, and scalability of memcached, but also the storage, persistence and querying capabilities of a database. The original membase source code was contributed by NorthScale, and project co-sponsors Zynga and Naver Corporation (then known as NHN) to a new project on membase.org in June 2010.[3]

On February 8, 2011, the Membase project founders and Membase, Inc. announced a merger with CouchOne (a company with many of the principal players behind CouchDB) with an associated project merger. The merged company was called Couchbase, Inc. In January 2012, Couchbase released Couchbase Server 1.8. In September, 2012, Orbitz said it had changed some of its systems to use Couchbase.[4] On December 2012, Couchbase Server 2.0 (announced in July 2011) was released and included a new JSON document store, indexing and querying, incremental MapReduce and replication across data centers.[5][6]

Architecture

Every Couchbase node consists of a data service, index service, query service, and cluster manager component. Starting with the 4.0 release, the three services can be distributed to run on separate nodes of the cluster if needed. In the parlance of Eric Brewer’s CAP theorem, Couchbase is normally a CP type system meaning it provides consistency and partition tolerance, or it can be set up as an AP system with multiple clusters.

Cluster manager

The cluster manager supervises the configuration and behavior of all the servers in a Couchbase cluster. It configures and supervises inter-node behavior like managing replication streams and re-balancing operations. It also provides metric aggregation and consensus functions for the cluster, and a RESTful cluster management interface. The cluster manager uses the Erlang programming language and the Open Telecom Platform.

Replication and fail-over

Data replication within the nodes of a cluster can be controlled with several parameters. In December 2012, support was added for replication between different data centers.[5]

Data manager

The data manager stores and retrieves documents in response to data operations from applications. It asynchronously writes data to disk after acknowledging to the client. In version 1.7 and later, applications can optionally ensure data is written to more than one server or to disk before acknowledging a write to the client. Parameters define item ages that affect when data is persisted, and how max memory and migration from main-memory to disk is handled. It supports working sets greater than a memory quota per "node" or "bucket". External systems can subscribe to filtered data streams, supporting, for example, full text search indexing, data analytics or archiving.[7]

Data format

A document is the most basic unit of data manipulation in Couchbase Server. Documents are stored in JSON document format with no predefined schemas. Non-JSON documents can also be stored in Couchbase Server (binary, serialized values, XML, etc.)

Object-managed cache

Couchbase Server includes a built-in multi-threaded object-managed cache that implements memcached compatible APIs such as get, set, delete, append, prepend etc.

Storage engine

Couchbase Server has a tail-append storage design that is immune to data corruption, OOM killers or sudden loss of power. Data is written to the data file in an append-only manner, which enables Couchbase to do mostly sequential writes for update, and provide an optimized access patterns for disk I/O.

Performance

A performance benchmark done by Altoros in 2012, compared Couchbase Server with other technologies.[8] Cisco Systems published a benchmark that measured the latency and throughput of Couchbase Server with a mixed workload in 2012.[9]

Licensing and support

Couchbase Server is a packaged version of Couchbase's open source software technology and is available in a community edition without recent bug fixes with an Apache 2.0 license[10] and an edition for commercial use.[11] Couchbase Server builds are available for Ubuntu, Debian, Red Hat, SUSE, Oracle Linux, Microsoft Windows and macOS operating systems.

Couchbase has supported software developers' kits for the programming languages .NET, PHP, Ruby, Python, C, Node.js, Java, Go, and Scala.

N1QL

A query language called the non-first normal form query language, N1QL (pronounced nickel), is used for manipulating the JSON data in Couchbase, just like SQL manipulates data in RDBMS. It has SELECT, INSERT, UPDATE, DELETE, MERGE statements to operate on JSON data. It was announced in March 2015 as "SQL for documents".[12]

The N1QL data model is non-first normal form (N1NF) with support for nested attributes and domain-oriented normalization. The N1QL data model is also a proper superset and generalization of the relational model.

Example

 
{
  "email": "testme@example.org",
  "friends": [
    {"name": "rick"},
    {"name": "cate"}
  ]
}
Like query
SELECT * FROM `bucket` WHERE email LIKE "%@example.org";
Array query
SELECT * FROM `bucket` WHERE ANY x IN friends SATISFIES x.name = "cate" END;

Couchbase Mobile

Couchbase Mobile is a suite of products to provide NoSQL databases and data replication for mobile and embedded devices.[13]

Couchbase Lite (originally TouchDB) provides native libraries for offline-first NoSQL databases with built-in peer-to-peer or client-server replication mechanisms.[14] Sync Gateway manages secure access and synchronization of data between Couchbase Lite and Couchbase Server.[15]

Bibliography
  • Brown, MC (June 22, 2012). Getting Started with Couchbase Server (1st edition). O'Reilly Media. p. 88. ISBN 978-1449331061.
  • Ostrovsky, David; Haji, Mohammed; Rodenski, Yaniv (November 26, 2015), Pro Couchbase Server 2nd ed. (2nd ed.), Apress, p. 349, ISBN 978-1484211861
  • Potsangbam, Henry (November 23, 2015), Learning Couchbase (1st ed.), Packt, p. 202, ISBN 978-1785288593
  • Vohra, Deepak (August 3, 2015), Pro Couchbase Development: A NoSQL Platform for the Enterprise (1st ed.), Apress, p. 331, ISBN 978-1484214350
  • Sangudi, Gerald; et al. (October 20, 2017), N1QL: A Practical Guide (2nd Edition) (2nd ed.), Self-published, p. 423
gollark: Also, IPv4 addresses are not very cheap.
gollark: I believe you'd need your ISP to allow BGP things which they probably don't.
gollark: It would be hard for them to introduce horrible bugs given that it's basically a Chromium wrapper, from the sounds of it.
gollark: It evaluates to what it's been set to, I suppose, so that's just always true.
gollark: Additionally, you don't need to do `A == true` as this is equivalent to `A`.

References
  1. Damien Katz (January 8, 2013). "The Unreasonable Effectiveness of C". Retrieved September 30, 2016.
  2. "NewProtocols - memcached - Klingon - Memcached - Google Project Hosting". Code.google.com. 2011-08-22. Retrieved 2013-06-04.
  3. Shashank Tiwari. Professional NoSQL. John Wiley & Sons. pp. 15–16. ISBN 9781118167809.
  4. "Balancing Oracle and open source at Orbitz". GigaOM. September 21, 2012. Retrieved September 19, 2016.
  5. Andrew Brust (December 12, 2012). "Couchbase 2.0 released; implements JSON document store". ZDNet.
  6. Derrick Harris (July 29, 2011). "Couchbase goes 2.0, pushes SQL for NoSQL". GigaOm. Retrieved September 19, 2016.
  7. Trond Norbye (March 15, 2010). "Want to know what your memcached servers are doing? Tap them". Couchbase blog.
  8. Frank Weigel (October 30, 2012). "Benchmarking Couchbase". Couchbase. Retrieved September 30, 2016.
  9. "Cisco and Solarflare Achieve Dramatic Latency Reduction for Interactive Web Applications with Couchbase, a NoSQL Database" (PDF). Cisco Systems. June 18, 2012. Archived from the original (PDF) on August 13, 2012. Retrieved October 7, 2016.
  10. "Couchbase Open Source Projects". Couchbase web site. Retrieved October 7, 2016.
  11. "Couchbase Server Editions". Couchbase.
  12. Andy Slater (March 24, 2015). "Ssssh! don't tell anyone but Couchbase is a serious contender: Couchbase Live Europe 2015". Retrieved February 13, 2018.
  13. "Couchbase Mobile Database - Android & iOS SQLite Alternative". www.couchbase.com. Retrieved 11 May 2020.
  14. "Lite | Couchbase". www.couchbase.com. Retrieved 11 May 2020.
  15. "Sync Gateway | Couchbase". www.couchbase.com. Retrieved 11 May 2020.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.