The Revolution in Database Architecture, by Jim Gray

Jim Gray's database architecture revolution explains that Gray believes it is an evolution of the database architecture since 2004. He believes the database has stagnated for several years and since 2004 the development of some technologies will pave the way for a revolution in the database world. The 14 technologies mentioned are the key to the revolution: the ability to execute object-oriented code in RDBMS. The database becomes a Web service.

What is more popular than Amazon's distributed data storage is the architectural model they think can be extended, that is, service-oriented architecture. As Werner Vogels pointed out in an interview with Jim Gray in 2006, Amazon noticed that he was working hard to expand the front end in 2001, and the service-oriented architecture eventually helped It was. This sentiment echoed from one engineer to the other until startups with only a few engineers and a few users began breaking their pamphlet application into nano services.

In the early days of my career I worked at a startup founded by some people with a doctorate in database architecture. Our products are special databases that can run certain types of queries in a fraction of the time in a relational database. We have never wondered how we built a product - we are database officials, we built a database - what is it used for? Of course the problem is that the world did not know that other databases are necessary. When we started a sales call and started with "We have a database ...", the potential customers explained to me how we differed from the database they already had I did not even let them in. You do not need to integrate other databases, other query languages, and other databases with the Oracle system. For the same reason, VC does not fund us - the database market is not growing, we can not prevail over Oracle in their own game, we do not have enough sales traction Hmm

The database world has revolutionized in recent years. Developers use NoSQL than traditional relational databases. In NoSQL, a more efficient and reliable new generation database has been confirmed. It is important to participate in this revolution and make the most of it. Dissatisfied, we started looking for data storage that meets our requirements. This is the time we met Aerospike. We are particularly interested in Aerospike LDT - Big data type. In the Aerospike LDT architecture, millions of small objects encapsulated as values ​​can be stored under the same key. Ideal for our use case