I have a scenario in which user uploads a file and a django app encodes the file into N distinct segments, each, to be stored on a different remote server. Say if we have 5 segments as the result of the encoding, from only 3 present segments, the file can be constructed (the reason for segmentation)).
the problem however is the distribution of the segments since it seems to be an unconventional way of storage in django; I consulted with the developer of django-Restro package and he suggested to write a django storage back-end from scratch which sounded a herculean task for me as a newbie in django and a close deadline.
After lots of digging someone suggested to use multiple databases and routing, I read the documentation in that regard and from what I grasped, multiple databases seemed to have other purposes. If this was the case, I think my scenario was easily achievable by defining one model per segment and link each to a corresponding database. Is it practical?
If not what way would you suggest for the storage part? My main struggle is in the part where the server wants to store each segment on a different remote server and later upon the user request, wants to retrieve them.
