Key Value Databases

All kinds of databases are used in the IT sector. Re­la­tion­al models are es­pe­cially popular as they make it possible to connect in­form­a­tion. There also other types, though, which provide special ad­vant­ages and so might be a better choice in certain situ­ations: NoSQL databases, document-oriented databases, column-oriented databases or graph databases. There’s also the Key Value Database. Here, a simple principle brings about tre­mend­ous per­form­ance.

Key Value Databases are based on a table with just two columns: In the first is the value, and the other contains a key, a distinct iden­ti­fic­a­tion mark. A value can take different forms. Very simple values like strings or integers are possible, but complex objects can also come up as values in the database. (The function or the position of the value can also occupy a document, for example, although then we would be talking about a document-based database.) Ref­er­ences to files can also be inserted into the database. Tuples—col­lec­tions of values—are also prac­tic­able.

The values in a database don’t have to be uniform. It’s possible to ac­com­mod­ate different objects in the same column. The same applies for the iden­ti­fic­a­tion marks. In most cases, the key will pre­sum­ably follow a certain pattern. In principle, though, it isn’t necessary. Strings and integers can also be con­struc­ted according to arbitrary criteria here.

The ad­vant­ages of Key Value Databases are their high per­form­ance and flexible scalab­il­ity, both of which stem from the model’s simple structure. As Key Value Stores don’t require or stipulate any uniform pattern, changes to the database can be made while in operation. It’s possible to introduce a new field while actions are happening in other entries at the same time.

The high speed makes this database model possible through the simple con­nec­tion of key and value. If you want to retrieve in­form­a­tion, you simply access the value directly via its specific key. The data is available directly. At the same time, though, this is a dis­ad­vant­age of the Key Value Store, as no other access method is available. Re­la­tion­al databases permit complex queries. The content of such databases can be sifted through in various aspects. In contrast, a Key Value Store only allows for access via the key. It’s generally necessary to do without further indices and search pos­sib­il­it­ies.

The ap­plic­a­tions of Key Value Stores are based on both their ad­vant­ages and their re­stric­tions. Key Value Databases are used whenever quick access times are needed for large quant­it­ies of data. For this reason, typical ap­plic­a­tions are shopping carts in online shops, or session data. Here, in­form­a­tion is clearly ordered and must be available in the shortest possible time. For large, well-known websites, these databases must con­stantly create new entries and delete old ones, something that Key Value Databases are perfectly adapted to.

There are now various database man­age­ment systems (DBMS) that are based on Key Value Databases.

• Amazon DynamoDB: The pro­pri­et­ary DBMS belongs to Amazon Web Services (AWS) and can also be used as a document-oriented database.
• Berkeley DB: This DBMS is developed by Oracle and provides in­ter­faces for the most varied pro­gram­ming languages.
• Redis: The open-source project Redis is one of the most-used DBMS and has already been used by Instagram and GitHub at an early stage.
• Riak: The DBMS Riak is available as an open-source version, as en­ter­prise software, or in the form of cloud storage.
• Voldemort: The dis­trib­uted DBMS is used and promoted by LinkedIn, among others.