Category: Application Design
Couchbase Eventing: small scripts that solve big problems
Eventing Simple Yet Powerful: Eventing allows small scripts to overcome hard to solve problems. If you are familiar with both Couchbase and Eventing please feel free to skip the brief overview and skip ahead to the examples. Overview: First off, let’s...
Implementing a robust portable cron like scheduler via Couchbase Eventing (Part 1)
This is the first of a multi-part series to leverage the Couchbase Eventing Service to run multiple scheduled tasks at specific recurring intervals in a cron like fashion completely inside the database without requiring additional infrastructure via a single general-purpose...
Replication in NoSQL document databases (Mongo DB vs Couchbase)
Replication has been a crucial part of Database Systems for decades for providing availability and disaster recovery. In recent times, with the evolution of distributed databases to address the need for highly available, scalable and globally distributed deployments operating across...
Part 2: N1QL: To Query or To Analyze?
When you need to query documents using SQL, there are two options available in Couchbase. The Query service and the Analytics service. Our blog, N1QL: To Query or To Analyze? provides a detailed overview of both services. I highly recommend...
Ingest data into Confluent Kafka via Couchbase Kafka Connector
Premise is very simple, in the world of disparate technologies where one does not works or integrates well together, Couchbase & Confluent Kafka are amazing products and are extremely complementary to each other. Couchbase is linearly scalable, distributed NoSQL JSON...
Customer 360 – Part 4 – Analyzing Your Data
OK, so we’ve looked at building aspects of a Customer 360 solution in previous posts. We looked at an overview of what’s involved in part 1, and since you’re reading this, I’m assuming that the threat of having to think...
Customer 360 – Part 3 – Mobile Integration
We’ve done a high-level overview of what’s involved in building a Customer 360 solution on Couchbase and all the thinking involved here… Then dug into the integration part of bringing in data from disparate sources and combining them in Couchbase,...
Customer 360 – Part 2 – Data Ingestion
So, we already took a high-level look at what’s involved in building a Customer 360 solution on Couchbase here. That’s right, it involved a lot of thinking. Sorry, no way around that. Ya gotta think, can’t be one of the...
Thinking About Customer 360
Customer 360. Or, as one of our competitors (who shall remain nameless, but uses a Birch leaf as their logo) calls it, Single View. Everyone wants it. Everyone needs it. After all, most of your customer data is stored in...
The Unreasonable Effectiveness of SQL in NoSQL Databases: A Comparative Study.
The business applications have requirements: take customer orders, deliver customer orders, track shipping, generate inventory report, end of the day/month/quarter business report, generate business dashboards and more. These requirements evolve slowly. They remain even when you choose a NoSQL database....
Search and Rescue: 7 Reasons for N1QL (SQL) developers to use Search
People don’t want a four key index. They need a four-ms response. Ted Levitt Application development is demanding. Each application is trying to progress on behalf of the customer — searching for the right product or the right form, ordering,...
Couchbase’s N1QL Query Shatters the Limits of MongoDB™
As NoSQL adoption grows, developers and enterprises alike require a general purpose database to replatform their mission-critical applications and services. These databases are no longer used only by backend services that need sub-second access to the data, but also by...