Online shops with millions of customers and products, social networks with huge numbers of members and complex network of relationships in which countless messages are exchanged, plus scientific projects in which measurement data is generated over measurement data … – The requirements for databases are enormous: They should be mountains of information Store them securely and, on request, make appropriate data available in a meaningful way in a matter of seconds. The stored information is often too unstructured to force it into predetermined schemes, and the interweaving between them is often incredibly complex.
Requirements that SQL databases fail to deal with – but which NoSQL databases can easily cope with: They are flexible, fast, scalable and can be used in a distributed manner. But … how do they actually do it? How do they store data, how do they access them and what fields of application are they suitable for? What are their advantages and disadvantages? To answer that, we’ll take a closer look at key-value, document-oriented, wide-column, and graph databases in this article.
- Access to all heise + content
- exclusive tests, advice & background: independent, critically well-founded
- Read c’t, iX, Technology Review, Mac & i, Make, c’t photography directly in your browser
- register once – read on all devices – can be canceled monthly
- first month free, thereafter € 12.95 per month
- Weekly newsletter with personal reading recommendations from the editor-in-chief
Start FREE month
Start your FREE month now
Already subscribed to heise +?
Sign up and read
Register now and read articles right away
More information about heise +