text excerpt from a book

results of SQL statements

HTML-files

audio

email

csv-data

video files

data from an excel sheet

JSON data

database tables

spoken text

XML-data

ACID support varies per solution

better in partition tollerance

better for clustered systems

good for semi-structured data

JOINS are not mandatory

relational

scales well horizontally

strict schema

full support of JOINS

good for structured data

stores data in a table

dynamic or flexivle schemas

fully supports ACID

new data properties can be added on the fly

Relationships are often captured by denormalizing data and presenting it in a single record

scales well vertically

select '{"a":1, "b":2}'::jsonb <@ '{"b":2}'::jsonb;

select '{"a":1,"b":2}'::json->>'b';

select '{"a":1, "b":2}'::jsonb ? 'b';

select '[1,2,3]'::json->2;

select '{"a":1, "b":2}'::jsonb @> '{"b":2}'::jsonb;

select '{"a":[1,2,3],"b":[4,5,6]}'::json#>>'{a,2}';

select '{"a":1,"b":2}'::json->'b';

select '[1,2,3]'::json->>2;

select '{"a":[1,2,3],"b":[4,5,6]}'::json#>'{a,2}';

The data might not be consistent immediately but eventually, it becomes consistent

The state of the system is always soft which means that it can change over time even if there are no reads or writes as the system keeps changing the data to make it consistent

when a database action is committed it forms the permanent state of database

parts of a transaction shouldn't commit if any one of them fails

any transaction should lead database from one stabe state to another

The system works well despite physical network partitions

true consistency cannot be achieved in a distributed environment

All clients always have the same view of the data

in a distributed system, a maximum of two of the three properties availability, consistency, partition tolerance can be guaranteed

Reads in the system are still possible even though they may not give the correct response due to inconsistency

Each client can always read and write

Either the whole transaction should succeed or it should be complete rollback

This is a typical example of ?

They are analogous to tables in a relational database

They are analogous to rows in relational databases

The right part of the tuple "4urjdjk633442 = 'Hello world'"

Must be unique

Can be used to identify a data record

The left part of the tuple "4urjdjk633442 = 'Hello world'"

Can be repeated

primarily uses SQL as query language

better matches horizontally

better matches vertically

uses tables, rows and columns to store data

a better fit for new projects with unclear schemas

a better fit for projects that need rigid schemas