Say YES! to NoSQL: A Guide on When to Ditch Relational Databases - Adrienne Tacke

Поделиться
HTML-код
  • Опубликовано: 4 дек 2024

Комментарии • 10

  • @user-pp5wl8zp8w
    @user-pp5wl8zp8w 3 года назад +3

    no need to worry, Adrienne , presentation is good and easy to understand

  • @d0vbysh
    @d0vbysh 3 года назад +2

    Well structured NoSQL introduction talk.
    Thank you!

  • @IAmFeO2x
    @IAmFeO2x 3 года назад +1

    Good talk. For me, the most important thing about document databases is that they avoid the Impedance Mismatch. Data is structured in a way that is more aligned with data in memory.

  • @natancieplinski4377
    @natancieplinski4377 3 года назад +3

    This was a great talk for someone that is not very familiar with NoSQL

    • @Tiptup300
      @Tiptup300 3 года назад

      What do you mean by that?

    • @Fafix666
      @Fafix666 3 года назад +1

      @@Tiptup300 I think he meant himself :)

  • @kairaja
    @kairaja 3 года назад +2

    Awesome presentation

  • @sasidharmanthripragada6873
    @sasidharmanthripragada6873 2 года назад

    Great presentation! Do you have a use case for going from NoSql to relational?

  • @williamb.2031
    @williamb.2031 3 года назад

    Fantastic!

  • @Fafix666
    @Fafix666 3 года назад +1

    It's an interesting and well structured presentation, as mentioned before, but the conclusions feel biased. I'm not a db expert by any means and it's been a while since I had to design one, so correct me if I'm wrong please. Wouldn't most of the relation db problems mentioned here, be solved by having modularized application with multiple databases? I understand that it's hard and may not always be possible or feasible, but it's completely ignored here.