Local/Server/SoundCloud/Mongo

jgroom33 / FitStormMK

FitStorm base using meteor kitchen

0 stars 0 forks source link

Local/Server/SoundCloud/Mongo #21

Closed jgroom33 closed 8 years ago

jgroom33 commented 8 years ago

This issue is to discuss the merits of each approach for cue and song storage.

SoundCloud

Benefits

API driven
minimal server processing
Drawbacks
requires data connection during app
Study

Does cue/song upload from mobile work?

Mongo

Benefits

Easy to add to app
Drawbacks
uploading from mobile doesn't work
bandwidth/processing power on app
Local

Benefits
Song/cues downloaded during app install
No server processing for pulling songs/cues
Drawbacks
app updates required for new media
Server

Benefits
Drawbacks
bandwidth/processing power on app
app updates required

cincochristopher commented 8 years ago

@jgroom33 Are we considering uploading the audio files on cloud storage like AWS S3 or Google Cloud?

I have researched on this package: https://github.com/CulturalMe/meteor-slingshot Its awesome cuz the file transfer occurs from your browser(client-side) directly to the cloud storage without even bothering the server. In that way we can lessen the load/processing of the server. What do you think?

jgroom33 commented 8 years ago

Sounds like a good alternative to SoundCloud. Have you ever used Spotify? I think what we're going to need is a local cache. So the app would come with 4-5 sets. Anything that is purchased gets downloaded and played locally.

cincochristopher commented 8 years ago

Yes. Im always using spotify. So you want to store the audio files in local cache just like spotify does ? is that right ?

jgroom33 commented 8 years ago

I think that will give the best performance and flexibility.

jgroom33 / FitStormMK