Articles


SQL is the only 22nd century tool available in 21st century

Here are the previous articles comparing architecture, database objects, data types, and data modeling of Oracle with Couchbase. This will focus on SQL support.  

Oracle was the first and staunch supporter of SQL. Oracle’s SQL implementation beat IBM to market by two years.  That changed the fortune of one or two people. :-) All of the modern relational databases implement SQL. So much so, the relational databases are sometimes called SQL databases, much to the chagrin of C. J. Date.  Nations are known by their languages… English, French, and American(!). It’s not a stretch for a class of database systems to be known by their languages as well.  SQL has been so effective, many big data and non-relational systems have picked up SQL as the lingua franca. SQL is here to stay, even for NoSQL systems. 

Source de l’article sur DZONE


Dynamo accelerated the NoSQL revolution that’s driving the database industry.

Recently, Amazon announced PartiQL – A SQL-Compatible Query Language for their flagship NoSQL database Amazon DynamoDB. This has brought the NoSQL “re:evolution” full circle. It’s wonderful to see the collaborative research from UCSD and Couchbase enabling the industry to move forward.

Source de l’article sur DZONE

For some time, products have been leaning towards NoSQL databases because of the number of advantages that they provide compared to Relational databases (RDBMS), especially in today’s distributed systemsThere is always a pressure of delivering things faster to make it live to end users. But does that mean relational databases won’t be able to compete with NoSQL databases, provided Relational Databases are still best-known for adhering to the ACID property?

Here, I am going to explore the possibilities from Relational Databases perspective and how they come a long way to compete with NoSQL Databases. I am going to compare two managed databases from AWS, DynamoDB and Aurora, to see if it’s really worth giving credit to one type of database over another.

Source de l’article sur DZONE

Let’s look at a Couchbase N1QL query.

A data construct that often appears in business applications is the hierarchical data structure. Hierarchy captures the parent-child relationship often between the same object. For instance, a company structure captures the reporting line between employees. A business organization captures the relationship between parent companies and subsidiaries. Territory hierarchies in Sales. Book of accounts in financial applications.

Due to the self-referencing nature of hierarchy, querying the structure efficiently along with its associated data can be a challenge for RDBMSs, particularly from a performance perspective. In this article, I will discuss how a traditional RDBMS handles hierarchical queries, the challenges that it has to deal with, and how this issue can be similarly addressed with Couchbase N1QL and Couchbase GSI.

Source de l’article sur DZONE