Don’t fret the relational database modeling. This is not your father’s SQL.
A constant debate regarding persistence layer, within engineering teams, when building a new product feature or a standalone service. Questions come up such as:
- Can my SQL layer handle the dynamic and flexible requirements?
- Will I end up building a Key-Value model?
- Should I use NoSQL or multi-model database?
- NoSQL will horizontally scales better, for sure, but can it handle my ACID transaction requirements and business…