Netflix System Design Architecture | OTT Video On Demand Platform | AWS | Video Streaming

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

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

  • @SudhaRajamanickam-pc9hd
    @SudhaRajamanickam-pc9hd Год назад

    Thanks for this video. Its really helpful. just one question, can we use just Opensearch and Redis alone for storing catalogue. why we need cassandra? can can store metadata as well in Opensearch itself right?

    • @ArchitectureBytes
      @ArchitectureBytes  Год назад +1

      While you could do that, please remember ...
      OpenSearch, being a search engine, is oprimized for data appends (as against updates/deletes) for eg ingesting logs, clickstreams etc. No transaction support either.

  • @niteshmethani9884
    @niteshmethani9884 Год назад

    This is a great tutorial. I specially liked the part where you went into details for each service flow. However, I am wondering if you could share some pointers on actually implementing these things. The architecture is currently on a blackboard. I would like to get hands-on and actually create this backend. Would appreciate if you could share any pointers around it.

    • @ArchitectureBytes
      @ArchitectureBytes  Год назад +2

      Glad you found this useful.
      You can implement one flow/microservice at a time.
      The Video Processing and Video Streaming flows are the important ones.
      Rest of the services are fairly straight forward.
      To understand AWS Media Services you can watch this:
      ruclips.net/video/jX2P1YHFuWY/видео.html
      There is an Audio/Video/Media playlist too - for similar content.

    • @niteshmethani9884
      @niteshmethani9884 Год назад

      @@ArchitectureBytes Thanks for the link. Will follow-up!

    • @humzaiqbal9908
      @humzaiqbal9908 Год назад

      @@ArchitectureBytes Thank you so much sir, you are doing great job,

  • @Nduzayani
    @Nduzayani 8 месяцев назад

    contacts please