Preamble  Couchbase Server can be used together with Elasticsearch. This makes quite sense because Full-Text-Search is not one of the main purposes of a Key-Value-Store. Instead an external (also scalable) search engine should be used in order to tokenize and index the data for full text search purposes. How it works with Couchbase is that you can install a transport plug-in to your Elasticsearch instance. You then can configure Couchbase's XDCR (Cross Data Centre Replication) feature in order to replicate the JSON documents to Elasticsearch and to let index your JSON data there. Then you can perform full text searches by using the Lucene Query Languge by getting the resuting keys (of Documents those are stored in Couchbase) back. Further details can be found at http://docs.couchbase.com/couchbase-elastic-search/ . Elasticsearch Basics Let's talk a bit about the Elasitcsearch terminology before we spot a light on Couchbase's default Elasticsearch configuration. Do...

This article should just explain what you need to do in order to use Couchbase Lite in your Android App. It is more or less following the tutorial of the documentation by summarizing it a bit. So what you need first is an Android project. I used Android Studio (and Gradle as the build framework). The build script is looking as the following one: Build script It shows which additional dependencies are required. Additionally you should download the following library and save it under the 'libs' directory of your project Additional dependency After you synchronized your Gradle project (All the other additional dependencies will be downloaded from the Maven repositories) you should be able to use the Couchbase Lite classes in your Android application. Let's begin with the Layout definition of our mobile app: Layout definition Our example app is just connecting to a database (by creating it) and then stores a document with a specific id. We will then retrie...

This post tries to give a short overview about the NoSQL market. It does not aim to be complete. It also gives you an idea of the several kinds of NoSQL approaches. So we will see that there is not in general the one and only NoSQL system. There are advantages and disadvantages. Key-Value Stores Key value stores are just that simple as they sound. If you know how a Java Map works, then you basically know the concept behind it. They allow you to store/update/retrieve values by keys. The key is often a string value (or a number, or a date). Because there has not to be a kind of specific container (like a table in the relational world) the key may follow conventions (E.G. 'houses:name:1' to store the name of the first house). Document oriented database systems could be seen as a special kind of database Key-Value Stores, because it just means that the value has the format of a JSON document. The major vendor seems to be: Riak:  This is a distributed Key-Value Store whereby a...

As far as I remember NoSQL meant originally just that no SQL is required in order to work with the underlying database system. I am sure that the most of you are knowing the S(tructured)Q(uery)L(anguage) from the relational database world. The theory behind it is based on the relational algebra. Since new (or even renewed) concepts are used for non-relational databases, also other ways to access data are used. In the meantime conceptional parts of the relational algebra were taken over to non-relational databases, too. So the 'No' stands now for 'Not only'.

This is a new blog with the subject NoSQL. The purpose of this blog is to post interesting news stories  and last but not least technical stuff about NoSQL stuff. The intended audience are newbies and advanced technical oriented persons. Why I am writing about NoSQL and Database stuff? Here some background information about me: From 2006 to 2010 I worked as a (Senior) Software Engineer for the Open Source database company 'Ingres' (now Actian). There I was responsible for Partner Certfication (Integration with partner products) and for Migration Tooling. Afterwards I joint the small NoSQL startup company 'sones'. The main product of 'sones' was the Graph Database System 'sones GraphDB'. There I was working as a Senior Consultant and Architect by beeing responsible for partner enablement, pre-sales and the architecuture and implementation of the persistent storage engine of the sones GraphDB 2.0 . Then I was working a while for a mid-siz...