Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
The whole thing feels like premature optimisation.
Pick a default setup:
A db for your metadata (I default to mongodb but whatever floats your boat at this point)
An object store for your audio files (here I default to s3)
Build a mvp, stress it bit and *then* replace whatever is necessary. Only this time you will have a much better idea of the problem you're trying to solve. -
@heyheni redis is more temporary, i don't want a key value store
@Commodore @12bitfloat thank you, i did my research and it looks ideal. do you know of any local software that can do the same as aws's object storage, so i can test the object storage locally? -
I have also seen, 1 db for meta data and other db instance for documents. Makes portability easier. This was pre cloud days
-
@calmyourtities depending on how close you want to mimic s3, you can have a look at one of those : http://s3-client.com/s3-compatible-...
Or onpenstack swift (https://wiki.openstack.org/wiki/...) which is s3 equivalent in onpenstack.
Related Rants
i'm starting a project where i will have a large amount audio clips, anywhere from a few seconds to about an hour long, and i need to store them based on which user created them and what group they are created in (so they will be sorted based on two integers). i'll need to concatenate and/or merge the audio files frequently, and i may need to filter which audio i use based on users and time created.
how should i store the audio? i'm pretty sure a database is the best option, but should i consider using the file system? if i shant, should i use mysql or postgres? i know postgres has more types and supports complex queries.
does anyone have experience who can help?
question
audio
mp3
data storage
postgres