Local Storage Naming and Directory Scaling #188
Labels
Discussion Needed
Require additional context and discussion
Enhancement
New features or upgrades for functionality, performance, etc
Priority: Backlog
Tasks that are not pressing, but to be tracked and revisited
Is your feature request related to a problem? Please describe.
Currently there is a static directory hierarchy that's constructed for local storage of videos, images, etc, on server startup.
While a fan-out is necessary to prevent overloading a single storage location (i.e. directory), we should (re)investigate this and consider refactoring as its somewhat inefficient and rigid for larger scale use-cases.
We also have a somewhat naive method for generating local path and file names that may have collision risks at larger scale that are not well articulated.
Describe the solution you'd like
Ideally we should have a methodology that is akin to consistent hashing in distributed storage. This lets us dynamically scale and adjust our hierarchy.
As for internal naming, we could look at UUIDs to be automatically generated.
The text was updated successfully, but these errors were encountered: