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:

  1. Can my SQL layer handle the dynamic and flexible requirements?
  2. Will I end up building a Key-Value model?
  3. Should I use NoSQL or multi-model database?
  4. NoSQL will horizontally scales better, for sure, but can it handle my ACID transaction requirements and business…

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store