- Database (keywords like select and from, insert update delete)
- store-> pre defined table values and column (table)
- row or record
- name column
- relational database (user order related by id and product )
- all record adhere to schema and need to be normalized
- one to one, many to many
- join (retrieved data into one table)
- data and schema
- relations
- not the best to perform reads
- data distributed in multiple tables
- horizontal scaling not supported for SQL
- vertical scaling (add pwr)
- complex queries with lots
- Mongo (humongous) database
- database
- collection of documents (collections)
- document
- field
- collection Documents -> (json style different schema) (person with a name another without a name)
- super flexible
- no relations in a NoSQL
- order collection for example (key data)
- less relation but super fast retrieval
- great for fast read
- easy to be split horizontally.
- great for read not the best for write given data being distrusted throughout.
- great performance No real winner