SQL is a standard language used by developers, DBAs, and business analysts to query data sets. Traditional SQL databases offer rich transaction capabilities, ad-hoc query and reporting capability, and vast amounts of standards-based tooling. Where they fall short is in the ability to scale out to meet the needs of modern, high-performance applications.
NoSQL was a solution to issues of scale that emerged as organizations began dealing with immense volumes, velocity, and variety of big data from a multitude of sources. NoSQL solutions offered availability, flexibility and scale. However, they came with difficult tradeoffs - sacrifice of data consistency and transactional (ACID) guarantees, loss of ad-hoc query capability and increased application complexity. Trading off data consistency and ACID in many cases means application developers, who are not distributed data infrastructure experts, have had to try and fill the gap. Now that you’ve got an overview of SQL vs NoSQL, who do you need to help you build and maintain your database systems? Relational and non-relational database management systems can get extremely complicated, and definitely require upkeep—especially when you factor in moving to the cloud. While it’s easy to manage a basic single-file database in a program you’ll want to hire a capable database architect to handle your relational database management system (RDBMS) or NoSQL database management.In 1972, Dr. Edsger Dijkstra wrote “The Humble Programmer,” in which he laid out his ideas about how to best write computer programs. Back in that world, programming was a big problem, particularly because the programmer was constrained by the computing power of the machine....
Despite multiple challenger technologies (eg. Object Oriented databases), the relational databases from Oracle, IBM and Microsoft have prevailed supreme for over 30 years....
The world has changed massively in the past 20 years. Back in the year 2000, a few million users connected to the web using a 56k modem attached to a PC, and Amazon only sold books. Now billions of people are using to their smartphone...
Editor’s note: This post is re-posted here by permission from the author. The original post was on LinkedIn on January 10, 2018. The world has changed massively in the past 20 years. Back in the year 2000, a few million users connected to the web using a...
Previously in part one of this blog series, I explained the problems with two methods of database interactions. Traditional JDBC-style interactions mean that locking and latching take up ~30% of compute time. This overhead skyrockets when you try to use a distributed system. A NoSQL key-value...
First off: I’m not here to bash NoSQL. NoSQL came into existence for a good reason — your generic legacy SQL RDBMS is often slow and expensive when compared to NoSQL alternatives. But much of the discussion I’ve seen about NoSQL, NewSQL, Legacy RDBMS and...
For decades, relational databases was the de-facto choice for financial service companies, until the 2000s where systems started to face challenges with scalability and availability as the amount of data being processed and consumed shaped how companies conducted their business. NoSQL databases emerged as a reaction...
Introduction NoSQL databases, such as Apache Cassandra, are often used in operational applications. However, a new breed of databases, such as VoltDB, are revolutionizing the fast data landscape. VoltDB is an in-memory NewSQL transactional database for fast data applications, currently in use by major telcos, financial...
In 2016, we partnered with Research Now to conduct a survey on a subject we take very seriously: data consistency. The results were shocking. While there was wide agreement on what is defined by “critical data” (financial data), only 58% of people surveyed stated that...
We looked at the basic differences between NoSQL and NewSQL in a recent post. Now let’s break the differences down specifically by looking at what developers really care about: Which problems can I solve with NoSQL? Equally important, where is NoSQL a bad fit? Where...