From the course: Choosing a Database: PostgreSQL, MySQL, Mongo, and Cloud

Comparing database options - SQL Tutorial

From the course: Choosing a Database: PostgreSQL, MySQL, Mongo, and Cloud

Start my 1-month free trial

Comparing database options

- [Narrator] When we're looking at data platform options we need to decide what kind of data model we want. This can be separated in two different kinds. Relational and non-relational data models. In the industry a non-relational database is sometimes called a NoSQL database. NoSQL is standing for Not only SQL. Although it is called a non-relational database it does store relational data sets. As data becomes more sophisticated and less structured, NoSQL databases provide more flexibility for developers to store data as they see fit. There are four main types. Document, key-value, wide-column, and graph databases. Document and key-value are more well know. In this course we'll be looking at MongoDB. Which is a document database. And here's an example of something we'll see later in the Mongo section. This is not to discount relational databases. Or also know as, SQL databases. And this is a screenshot of something we'll be looking at in the Postgres section. An older and still extremely popular data model, relational databases uses SQL to make accessing easy and organized. Since data is stored in fixed tables in columns. The fixed structure is very good for data integrity. Although it leaves less flexibility for scaling horizontally. We'll talk more about relational database specific assets. Such as different transactions, (inaudible), and indexing. Both come with it's own pros and cons. We'll be reviewing some of the most well known vendors of the relational and non-relational database. And how to find the best fit for you.

Contents