In the first part, we looked at the basic mechanics of MySQL and Couchbase Server 2.0, and compared the ways in which you would model the data, and how the basic queries and lists of records operate, from the MySQL SQL statement, to the Couchbase Server View.
Moving from a relational database, like MySQL, to a NoSQL database, like Couchbase, requires that you change the perspective on your data. In this article, MC Brown explains the differences between structuring data for a MySQL and a Couchbase database. He also discusses how these differences impact your queries.
This is a quick overview of Couchbase NoSQL, the ecosystem and what it means to developers, architects and implementers. We will demonstrate with examples of how to use the different language APIs with liberal but simple code examples on Couchbase to drive home some of these concepts. We will also …
Couchbase Server provides a simple, distributed document store. Written in a combination of Erlang using components of OTP for clustering and supervision alongside some C/C++, Couchbase Server manages the distribution of documents across a cluster of commodity hardware allowing for indexing of these documents and analytics through views. The system …
Matt Ingenthron of Couchbase presents the UnQL language. UnQL means Unstructured Query Language. It’s an open query language for JSON, semi-structured and document databases. This language is the brainchild of Richard Hipp, the creator of SQLite, and Damien Katz, CTO of Couchbase and creator of CouchDB.
