These data stores are shemaless or schemafree, meaning that the records in the same logical container (table or collection or ...) can be of a different structure each. In other words, two consecutive records can have different number of columns, each of different type. More, each column can hold another record with its own set of columns, creating nested records.

A bit of wording ...

/bigdata/nosql/introThe Big Data ecosystem consists of multiple products, each of them having some or all the characteristics we were evoking in our definitions. Not only they will handle high volumes of data, but they will allow you to process data without specific schema (Variety) quickly (Velocity). This is a list of products and a short description of what they do.

Storage is a key component of any system. We have heard a lot about storage.
But what is what ? Local storage versus remote storage.
Block storage, file storage, object storage, ... what's the differences ?
Let's try to raise a bit of the curtain on the storage aspect of your infrastructure.

In the section, we will cover the technical aspects of the implementation of various solutions to create working high-available setup. This are technical howto's covering some particular aspect(s) of the software in use, to achieve a given goal.

All the pratical howto's in this section are based on the following software :

One of the core components in any enteprise is the CMDB (Configuration Management DataBase). The CMDB is not just an inventory tools listing all the elements you have in your infrastructure, it is also a tool showing the dependencies between them.
Even in the case of small infrastructure, it is valuable to have in place a good inventory tools with dependency links between the elements.
In such CMDB tools, each componant is called "Configuration Item" or CI. A CI may be a server or a CPU in a server, a software, ...