Planet NoSQL

As an application architect, eventually, you’d choose the database or database service to power your newest application or a microservice. Selecting one of the databases among relational databases was easier. The use cases were roughly divided into OLTP and OLAP (decision support). The workload differences between OLTP and OLAP were well known. OLTP workloads consist of short transactions on few random rows, expecting millisecond responses on pre-compiled queries; OLAP workloads consist of data loads, long-running queries scanning millions of rows of a fact table of a star/snowflake schema. Each had the performance benchmark and TCO well defined, measured and audited via TPC benchmarks . You can make use of these numbers, approximate your workload, understand the needs and capabilities match on other fronts like administration. Then, there are NoSQL databases. NoSQL databases were invented to handle the webscale performance of operational applications. It had to be elastic to handle ...

As an application architect, eventually, you’d to choose the database or database service to power your newest application or a micro-service. Selecting one of the databases among relational databases was easier.  The use cases were roughly divided into OLTP and OLAP (decision support). The workload differences between OLTP and OLAP were well known. OLTP workloads consist of short transactions on few random rows, expecting millisecond responses on pre-compiled queries; OLAP workloads consist of data loads, long-running queries scanning millions of rows of a fact table of a star/snowflake schema. Each had the performance benchmark and TCO well defined, measured and audited via   TPC benchmarks .  You can make use of these numbers, approximate your workload, understand the needs and capabilities match on other fronts like administration.   Then, there are No-SQL databases. NoSQL databases were invented to handle the webscale performance of operational applications. ...

[This article is a repost of my article at DZone at:  https://dzone.com/articles/how-couchbase-won-ycsb ] We chose to run YCSB  and do the other performance work in Couchbase 4.5. Not because it's easy, but because it's hard; because that goal served us to organize and measure our effort and features and hold them to a high standard. Like all the  good benchmarks ,  YCSB  is simple to support and run.  Most NoSQL can run YCSB  benchmarks. The difficulty is in getting those numbers high. Just like the TPC wars in 90s, the NoSQL market is going through its YCSB wars to prove the performance and scalability. Cihan Biyikoglu has discussed the  combination of technologies  within Couchbase helping customers scale and perform. In this article, we'll focus on Workload-E in YCSB — How Couchbase is architected and enhanced in  Couchbase 4.5 to win this round of YCSB  against MongoDB. Figure 1 Couchbase Architecture. To put ...