Suitable or not suitable

You learned when key-value databases are suitable and when not.

Can you place the following cards in their correct category?

Este exercício faz parte do curso

NoSQL Concepts

Exercício interativo prático

Transforme a teoria em ação com um de nossos exercícios interativos

Começar o exercício

Este exercício faz parte do curso

NoSQL Concepts

IntermediárioNível de habilidade

4.8+

Iniciar curso de graça

To begin the course, you’ll learn the differences between NoSQL and relational databases. After that, you'll discover key-value databases, their advantages, and their limitations. You’ll recognize the situations in which key-value databases are suitable. You’ll end this chapter by studying the case of Editoo, a company that reduced its downtime and improved its performance thanks to the Redis key-value database.

Exercise 1: Welcome!Exercise 2: NoSQL vs relational databases Exercise 3: Keys and values Exercise 4: Advantages and limitations of key-value databases Exercise 5: Classifying advantages and limitations Exercise 6: True or false?Exercise 7: When to use key-value databases Exercise 8: Appropriate use cases Exercise 9: Suitable or not suitable

Exercício atual

Exercise 10: Redis case study Exercise 11: Redis features Exercise 12: Redis and Editoo

In this chapter, you'll learn the basics of document databases. Then, you'll identify the advantages and limitations of this kind of database, and you’ll recognize the situations in which document databases are suitable. Finally, you’ll end this chapter with the Shutterfly case study. They used the MongoDB document database to reduce latency and accelerate time to market.

Exercise 1: What is a document database?Exercise 2: Documents or collections?Exercise 3: True or false?Exercise 4: Key-value or document database?Exercise 5: Advantages and limitations of document databases Exercise 6: Classifying advantages and limitations Exercise 7: Examining the advantages and limitations Exercise 8: When to use document databases Exercise 9: Appropriate use cases for document databases Exercise 10: Suitable or not suitable Exercise 11: MongoDB case study Exercise 12: MongoDB features Exercise 13: MongoDB products Exercise 14: Shutterfly and MongoDB

You'll look at column family databases, analyzing the advantages and limitations of this kind of database. You'll also study the situations where column family databases are suitable. Finally, you'll end this chapter with the case study of Bigmate, a company that used the Apache Cassandra database to handle millions of operations by concurrent users each second.

Exercise 1: What is a column family database?Exercise 2: Identifying column family components Exercise 3: True or false?Exercise 4: Identifying the database Exercise 5: Advantages and limitations of column family databases Exercise 6: Classifying advantages and limitations Exercise 7: Examining the advantages and limitations Exercise 8: When to use column family databases Exercise 9: Appropriate use cases for column family databases Exercise 10: Suitable or not suitable Exercise 11: Apache Cassandra case study Exercise 12: Cassandra features Exercise 13: Bigmate and Cassandra

This final chapter analyzes graph databases. You'll study the advantages and limitations of this kind of database and the situations where these are most useful. You'll end this course by looking into Gousto, a company that obtained better cost control thanks to the Neo4j database.

Exercise 1: What is a graph database?Exercise 2: Identifying graph database components Exercise 3: True or false?Exercise 4: Identifying the database Exercise 5: Advantages and limitations of graph databases Exercise 6: Classifying advantages and limitations Exercise 7: Examining the advantages and limitations Exercise 8: When to use graph databases Exercise 9: Appropriate use cases for graph databases Exercise 10: Suitable or not suitable Exercise 11: Neo4j case study Exercise 12: Neo4j features Exercise 13: Neo4j graph platform Exercise 14: Gousto and Neo4j Exercise 15: Congratulations!