Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system, and reading the same back upon request. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal or current file locations for the file or file chunks to be stored within the file storage system. These optimal or current locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to or read the file from the file storage system. The file write may be validated and finalized, and the successful write or read may be displayed to the user on a user interface on a client.

Abstract: Systems and methods of the present invention provide for a user requesting a file or a plurality of file chunks stored in a file storage system, and a customized metadata stored in data storage. One or more tracker servers may determine file locations in the file system, and the location of the customized metadata in the data storage. These locations may be returned to an application, possibly an API, which may determine one or more URLs for the file locations and perform an HTTP request to read the file or file chunks from the locations or URLs in the file system. The file or file chunks, along with the customized metadata, may then be returned and displayed to the user that requested them.

Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal file locations for the file or file chunks to be stored within the file storage system. These optimal locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to the file storage system. The file write may be validated and finalized, and the successful write may be displayed to the user on a user interface on a client.

Abstract: Systems and methods of the present invention provide for a user requesting a file or a plurality of file chunks stored in a file storage system, and a customized metadata stored in data storage. One or more tracker servers may determine file locations in the file system, and the location of the customized metadata in the data storage. These locations may be returned to an application, possibly an API, which may determine one or more URLs for the file locations and perform an HTTP request to read the file or file chunks from the locations or URLs in the file system. The file or file chunks, along with the customized metadata, may then be returned and displayed to the user that requested them.

Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system, and reading the same back upon request. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal or current file locations for the file or file chunks to be stored within the file storage system. These optimal or current locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to or read the file from the file storage system. The file write may be validated and finalized, and the successful write or read may be displayed to the user on a user interface on a client.

Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal file locations for the file or file chunks to be stored within the file storage system. These optimal locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to the file storage system. The file write may be validated and finalized, and the successful write may be displayed to the user on a user interface on a client.