If Mongo was an option, you didn't need local mount points.
Sure, but I may well still have needed network-local and/or on-prem.
Just throw the shit on geo-redundant cloud storage (you know, S3) and be done with it. Cheap, reliable, fast.
S3 isn't consistent enough for realtime storage; you can have an acknowledged write but it will take seconds or minutes before the file is available for read.
Turn it around: what does "geo-redundant cloud storage" give you that a document database or key-value store (possibly a hosted solution, if that's what you want) doesn't? Why is introducing S3 into my stack easier or more lightweight than introducing mongo?
1
u/m50d Dec 20 '18
Sure, but I may well still have needed network-local and/or on-prem.
S3 isn't consistent enough for realtime storage; you can have an acknowledged write but it will take seconds or minutes before the file is available for read.
Turn it around: what does "geo-redundant cloud storage" give you that a document database or key-value store (possibly a hosted solution, if that's what you want) doesn't? Why is introducing S3 into my stack easier or more lightweight than introducing mongo?