locked
Video Asset Management RRS feed

  • Question

  • I apologize in advance for the noob question, but I am a noob on windows azure.

    I am building a site for a client who wants to organize videos by content, in this case lead actor in that video. Each actor may have multiple videos. Each actors videos will be access on the web using a single directory, so the url would be something like www.siteaddress.com/actorname.

    Should I make each video an asset, or each collections of videos an asset? They will all be the same type of video, h.264.

    Thanks!



    • Edited by agedgouda Monday, December 16, 2013 8:50 PM
    Monday, December 16, 2013 8:50 PM

Answers

  • Hello,

    If I were you I would do each video is an asset. 
    And use table storage to store video url by actors.

    It would be easier to add new video and query

    • Marked as answer by agedgouda Tuesday, December 17, 2013 2:30 AM
    Monday, December 16, 2013 9:31 PM

All replies

  • Hello,

    If I were you I would do each video is an asset. 
    And use table storage to store video url by actors.

    It would be easier to add new video and query

    • Marked as answer by agedgouda Tuesday, December 17, 2013 2:30 AM
    Monday, December 16, 2013 9:31 PM
  • Thanks for the quick response! Would it be ok to use a mongodb (I have more experience with that), or should I stick with table storage? Is there a difference in terms of performance?

    Thanks again, this is a huge help!

    Monday, December 16, 2013 10:52 PM
  • Hello,

    I would say go for azure table because it's probably more cost effective and less deployement.

    mongodb is perfectly find but you will probably have to deploy it on worker role or VM, scale it, maintain it.
    see http://docs.mongodb.org/ecosystem/platforms/windows-azure/

    azure table is realy easy to pick up and well documented it should be quite simple

    g
    ood luck

    Tuesday, December 17, 2013 9:00 AM