FastDFS is an open source distributed file system similar to Google FS. It is implemented in pure C language and supports UNIX systems such as Linux, FreeBSD, and AIX. It can only access files through proprietary APIs, does not support POSIX interface, and cannot be used by mount. To be precise, Google FS and Google FS like FastDFS, mogileFS, HDFS, TFS are not system-level distributed file systems, but application-level distributed file storage services.
FastDFS is an open source distributed file system. It manages files. Its functions include: file storage, file synchronization, file access (file upload, file download), etc., which solves the problem of mass storage and load balancing. It is especially suitable for online services with files as the carrier, such as photo album websites, video websites and so on.
FastDFS is tailored for the Internet, fully considering mechanisms such as redundant backup, load balancing, and linear expansion, and pays attention to indicators such as high availability and high performance. It is easy to build a high-performance file server cluster with FastDFS to provide file upload and download. and other services.
The astDFS server has three roles: tracker server, storage server, and client.
tracker server: Tracking server, mainly for scheduling and load balancing. The state information of all storage groups and storage servers in the cluster is recorded in memory, which is the hub for the interaction between the client and the data server. Compared with the master in GFS, it is more compact, does not record file index information, and occupies a small amount of memory.
storage server: storage server (also known as storage node or data server), files and file attributes (meta data) are saved to the storage server. The storage server directly utilizes the OS file system calls to manage files.
client: The client, as the initiator of the service request, uses the TCP/IP protocol to exchange data with the tracker server or storage node through the proprietary interface.
FastDFS server roles: tracker and storage node. The tracker mainly does scheduling work and plays the role of load balancing in access.