Next Generation Databases: NoSQL, NewSQL, And B...
Looking back at the report with which we introduced the term NewSQL, it is clear that the early NewSQL pioneers failed to have a material impact on the database market. It is especially telling to compare the survival rate of those early NewSQL players with the various NoSQL vendors that were also mentioned in the report. As such, it would be easy to conclude that NewSQL was a relative failure. However, that would be to overlook the complexity of what the various NewSQL database players were trying to achieve, as well as the lessons learned by the second generation of 'distributed SQL' vendors, which represent the evolution of one subset of the overall NewSQL category. Customer demand for globally distributed databases, especially those delivered as a service, is now significantly stronger than it was a decade ago, while the newer vendors have also learned from the success of the NoSQL vendors to focus not only on the technical elegance of their databases, but also developer engagement and ease of consumption. The term NewSQL may not survive the next decade, but its impact will be felt on the database market for many years to come.
Next Generation Databases: NoSQL, NewSQL, and B...
The next generation of distributed relational database vendors has fared better, however. Cockroach Labs has more than 300 customers and a $2bn valuation; PlanetScale recently announced the launch of its developer-focused database service; and PingCAP launched the public preview of its TiDB Cloud managed service, having launched version 2.0 of its database in 2020 and raised a $270m series D funding round.
Working with next generation databases like MongoDB has been a lot of fun, but did make me realise how much need there is for a strong tooling ecosystem around these new databases. I like to think that I made significant contributions to tooling for relational databases and had a strong desire to build something for post-relational systems.
Google has recently announced that its flagship wide-area database named Spanner has been made available on the Google Cloud. Google Spanner is the next generation globally-distributed database built inside Google and announced to the world through the paper published in OSDI 2012 [1]. This article explores the implication of Google Spanner, in particular to the NoSQL world.
The graph database is a critically important new technology for data professionals. As a database technologist always keen to know and understand the latest innovations happening around the cutting edge or next-generation technologies, and after working with traditional relational database systems and NoSQL databases, I feel that the graph database has a significant role to play in the growth of an organization. Not only are traditional database systems generally inefficient in displaying complex hierarchical data, but even NoSQL lags a little. We usually see a degradation in performance with the number of levels of relationship and database size. Also, depending on the relationship, the number of joins may increase as well.
As big data continues down its path of growth, there is no doubt that these innovative approaches – utilizing NoSQL database architecture and Hadoop software – will be central to allowing companies reach full potential with data. Additionally, this rapid advancement of data technology has sparked a rising demand to hire the next generation of technical geniuses who can build up this powerful infrastructure. The cost of the technology and the talent may not be cheap, but for all of the value that big data is capable of bringing to table, companies are finding that it is a very worthy investment. 041b061a72