In this course, we will introduce you to some common types of databases. Different data problems can be solved in a wide variety of ways, which is why so many different types of databases exist. After learning about a few different types of databases, you’ll be ready to explore specific implementations further.
During this course, I’ll introduce you to the following:
- SQL databases
- Key-value databases
- Graph databases
This course is for novice:
- Software engineers
- Data engineers
- DevOps engineers
- Site reliability engineers
- You should have at least a conceptual understanding of programming and be comfortable with data structures, data types, etc.
The goal for this course was to introduce you to some common types of databases. We covered:
Let’s run through some of the key takeaways from this course for each database. Relational databases are a type of database which represents data in terms of tables, columns, and rows. Tables are used to model specific concepts. Columns describe an attribute of the concept being modeled. They include names, data types, and optional constraints. Rows are collections of columns representing a single instance of a concept.
Concepts which cannot be modeled effectively using a single table can be broken down into multiple interconnected tables. Which is a common practice when following database normalization best practices. Relational databases are commonly programmed using the domain-specific language: SQL.
SQL is used to create and control relational databases using a minimalist English-like syntax. The structure of a database is called a schema. SQL databases codify data integrity rules into the schema. Allowing the database to be responsible for its own data integrity. SQL databases have many use cases ranging from data exploration and visualization to application storage, and many others.
A few common examples of SQL databases include:
Key-value databases are collections of key-value pairs of data. They can set, get, and remove value data based on a key. They don’t typically include a query language. Rather they tend to provide either a client library or command line interface. Key-value databases are basically giant lookup tables. Which makes them useful to engineers for many different use cases. For example, data caching, centralized metadata lookup, embedded application storage, etc.
A few common examples of key-value databases include:
Document-oriented databases are databases whose fundamental unit of data is called a document. Documents consist of attributes which describe the concept being modeled. Documents exist inside of a collection. A collection is just a namespace for a group of related documents.
Documents inside of a collection aren’t required to use the same set of attributes. Document-oriented databases are considered to be schemaless because they don’t enforce any constraints when the data is saved to the database. This flexibility shifts the burden of data integrity from the database to the developer.
Many document-oriented database implementations represent documents using JSON or a similar format. Though query mechanisms vary across implementations. Document-oriented databases are commonly used for: iot, game development, catalogs, mobile applications, event logs, etc.
A few common examples of document-oriented databases include:
Graph databases are used to store and explore data and its relationships. Data is stored as nodes and edges. Nodes model concepts using properties and labels. Edges model relationships between nodes. Edges may or may not include a direction depending on the use case and database implementation.
Graph databases don’t have a standard query language. A few common language examples include:
Being able to model data and relationships has a wide range of use cases including fraud detection, recommendation engines, social networks, network topologies, and the list keeps going. A few common examples of document-oriented databases include:
Working with data is part art and part science. The science part comes in the form of the engineering efforts that go into data structures, efficient data retrieval, query languages, etc. The art of it comes in the form of a holistic understanding of your specific use case. The better you understand your use case, the better you’ll be able to model and consume your data.
Hopefully, this course has given you a glimpse into the world of databases. There are many different types of databases; each with its own set of tradeoffs. And this course only scratches the surface of the capabilities of these databases.
If you’re interested in learning more about any or all of these databases I recommend installing and exploring them for yourself. Hands-on learning will help you to more fully understand the capabilities of these systems.
Okay, that's going to be all for this course. Thank you so much for watching. And I’ll see you in another course!
Ben Lambert is a software engineer and was previously the lead author for DevOps and Microsoft Azure training content at Cloud Academy. His courses and learning paths covered Cloud Ecosystem technologies such as DC/OS, configuration management tools, and containers. As a software engineer, Ben’s experience includes building highly available web and mobile apps. When he’s not building software, he’s hiking, camping, or creating video games.