---
# System prepended metadata

title: ':rocket:  POSTGRES JSON ? :rocket:'

---

# :rocket:  POSTGRES JSON ? :rocket: 

with the new notification politics, we have to store data about sended notidfications.

we have to solutions, follow usual in lifeaz with postgres sql shemas or postgres nosql json shema


## postgres sql shemas 

### exemple of table struct 
 
| idSendedNotif | date       | user | ... |
|---------------|------------|------|-----|
| 12            | 12.12.2012 | 0289 | ... |
| 398           | 12.12.2013 | 1426 | ... |
| 234           | 13.13.24   | 930  | ... |


### advantages
* solid data structure
* consitent datas
* powerful queries

### disavantages 
* low flexbility 
* low scalability
* low evoution capacity


## postgres nosql shemas 

### exemple of table struct 
 
| idSendedNotif | datas      | ?userId |
|---------------|------------|------|
| 12            | {date: xxxx} | 0289 |
| 398           | {date: xxxx} | 1426 |
| 234           | {date: xxxx}   | 930  |


### advantages
* flexibility and evolutions
* replicability and scalling

## disavantages 
* lower query possibillity
* less data consistence



##  conclusion for me 

we need to store rows that will be fully updated for each update so powerfulls queryLanguage is not realy required

we need a big data structure evolution capacity becose we don't now whats new critary will apear and we don't wants to update all datas at each structure evolution;

then for me postgres json table is a really good solution.

