This family consists of NoSQL data stores crafted for one specific goal, the indexing and search into their data content using complex, full-text and / or distributed search queries.
These data stores only contain pairs of keys and values. Values can only be retrieved when the key is known.
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 ...
Database or data store. Is there a difference?
Yes, as per the following definition, found on Wikipedia:
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.
All the pratical howto's in this section are based on the following software :
Distribution: CentOS 6 64 bits
Other repositories in use : EPEL, RPMforge
- Document management systems : where you will have versioning of documents, workflows, check out / check in possibilities, integration within the Office applications
- Web forums : create threads of conversation with a web browser, post answers or questions, search for pertinent information
- Wiki : share your knowledge by creating / modifying / deleting articles on web site.
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, ...