These are very interesting questions:
-
The sunshare backend is made of 2 pieces:
A sunshare BTFS node to interact with the BTFS Network and upload files to the network
A sunshare API is used by the frontend, acting as a middleware between the frontend and the sunshare BTFS node.
Once the project is production-ready, I am planning to spawn 3 sunshare BTFS Nodes and 3 sunshare APIs for high availability.
If this is still not enough to handle the traffic, I am planning to use sunshare demand as a parameter for the Share price cost computation, the same way a blockchain calculates gas fees. The busier sunshare is, the higher the price will be. -
BTFS will be able to handle a large demand. There is currently 607.10 PiB of free
space on the network and more than 1500000 “super” miners (nodes with a good reputation used by sunshare to store files’ copies) -
Sunshare uses file CIDs generated by BTFS to fetch files, these CIDs are a hash of the file content. If a file is corrupted, the CID will not match anymore. Moreover, sunshare uploads 3 copies of the same file into the BTFS network, meaning that if one copy gets courrupted, sunshare can still have access to 2 other copies.