"Distributed Object Storage - Go principles of architecture and language."

__ Download: HTTP: // gqylpy / DI / 278__

A distributed storage architecture consists of three parts: the client, a metadata server and the data server. The client is responsible for sending read and write requests, the cache file metadata and file data. The metadata server is responsible for managing metadata and processing the client's request, is a core component of the whole system. The data server is responsible for storing file data, to ensure the availability and integrity of data. The benefit of this architecture is able to simultaneously expand the performance and capacity, size of the system has strong scalability.
The most common object storage solution that multiple servers built-in high-capacity hard disk, and then loaded on the object storage software, and then do a few extra serving as a management node, installed on the target storage management software. Management node can manage other servers provide external read-write access.
The reason why there has been an object store this kind of thing, in order to overcome the disadvantages of each block storage and file storage, Talia carry forward their respective advantages. In short block storage fast read and write, is not conducive to sharing, file storage read and write slow, is conducive to sharing. You can get a quick read and write, which will help share out of it. Then there is the object store.

Guess you like

Origin www.cnblogs.com/gqy01/p/11301913.html
Recommended