Category: Data Modeling

Moving from MongoDB to Couchbase server (revisited)

Moving from MongoDB to Couchbase server (revisited)

Note: this blog post is a revist of Matthew Revell’s Moving from MongoDB to Couchbase Server This is a developer-focused guide to moving your application’s data store from MongoDB to Couchbase Server. If you’re interested in migrating from a relational...

ELT processing with Couchbase and N1QL

ELT processing with Couchbase and N1QL

Moving data between data sources. This is one of the key activities in data integration projects. Traditionally, techniques around data movement has been part of Data Warehouse, BI and analytics. More recently Big Data, Data Lakes, Hadoop, are frequent players...

Using Couchbase to Store Non-JSON Data

Using Couchbase to Store Non-JSON Data

I believe most of the power of Couchbase Server comes when you use it as a document database to store JSON documents. You get to use N1QL, for instance! However, there are some times when you need Couchbase to store...

October 7, 2016
SQL for JSON and Full Stack Development – August 2016, Tulsa Tech Fest (Videos)

SQL for JSON and Full Stack Development – August 2016, Tulsa Tech Fest (Videos)

I was a speaker at the Tulsa Tech Fest on August 5th, 2016. I had a great time, met a lot of new people, and talked a lot about Couchbase. It’s rare for me to go to a conference or...

September 1, 2016
Model Your Relational Database Data as NoSQL Document Data

Model Your Relational Database Data as NoSQL Document Data

When I’m presenting at events, I often get questions around data modeling.  It is common to interact with developers that work with relational databases, but are very interested in a NoSQL database.  I, for example, started my database career with...

Couchbase Server 4.5’s new Sub-Document API

Couchbase Server 4.5’s new Sub-Document API

Introduction Couchbase Server 4.5 has just been released, so let’s try it out! A complete overview of all the great new features can be found here. This article will highlight the new Sub-Document API feature. What’s a sub-document? The following document...

Couchbase with Windows and .NET – Part 4 – Linq2Couchbase

Couchbase with Windows and .NET – Part 4 – Linq2Couchbase

Part 1 covered how to install and setup Couchbase on Windows Part 2 covered some Couchbase lingo that you’ll need to know Part 3 showed the very simplest example of using Couchbase in ASP.NET In this blog post, I’m going...

May 18, 2016
Exploring Couchbase and N1QL through Touchbase using Node.js and Angular.js – Part 5: Graphing User Data

Exploring Couchbase and N1QL through Touchbase using Node.js and Angular.js – Part 5: Graphing User Data

Part 5: Graphing Necessary Materials: Node.js Express Chart.js Node Modules Used: tc-angular-chartjs body-parser moment.js Summary: To maintain a social network, and improve the experience for an end-user, it’s important to keep track of information about these users and their usage...

April 3, 2016
Document Database Granularity Level for the Relational Minded in 2 Minutes

Document Database Granularity Level for the Relational Minded in 2 Minutes

When we explain what is NoSQL, and how Couchbase fits in that picture, we usually get questions about Relational Databases, and we can't avoid comparing the two. While their architecture are quite different, we can find some similarities in concepts....

Moving from Oracle to Couchbase

Moving from Oracle to Couchbase

Oracle was the first database I developed with, so I know that thinking about switching to something like NoSQL and leaving behind the relational model can seem like a scary thing. The thing is, it really wasn’t scary when I...

Full Stack Development with the CEA2N Stack Webinars

Full Stack Development with the CEA2N Stack Webinars

Although slightly late on this post, I thought it would great to share that I’m presenting a five-part webinar series on the topic of full stack development. Now the first episode did already happen, but the great thing is that...

Data modelling for N1QL

Data modelling for N1QL

In my posts on key-value data modelling with Couchbase, the main concerns were: * when to embed data and when to refer * building secondary indexes * key design. In a N1QL world, we’re still thinking about similar things and in this post...