When I asked why you don't use nosql

  • 1

    we were using documentDB and Azure SQL.

    Document DB for some of fluid data which changes quickly (Like user profiles, settings, other things like that)

    SQL was used for "tabled" data to allow fast search and agregation (sums, averages etc).

    Finally we integrated everything present in documentDB into SQL server as a JSON columns.

    The life of devs got so so so much easier.

    Ofc, it all depends on your neededs, but I feel like JSON/XML column in SQL can cover the basic need of storing serialized data which can quickly evolve at code side
  • 2
    My ex project manager : " let's use Excel for database instead"
  • 0
    @NoToJavaScript Came here looking for the JSON comment.
Add Comment