Skip to content

Commit cd1ece3

Browse files
committed
docs: refine documentation for internationalization and fix copy-paste errors
1 parent 3e892b0 commit cd1ece3

File tree

35 files changed

+255
-260
lines changed

35 files changed

+255
-260
lines changed

docs/about/index.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
# About Us
22

3-
**RustFS is committed to becoming a world-leading company in data security and cost reduction.**
3+
**RustFS is dedicated to leading the industry in data security and cost-efficiency.**
44

5-
RustFS is a world-renowned open-source infrastructure solution for distributed object storage. It is a project jointly initiated and composed of talented storage architects and open-source enthusiasts from across the globe. Our core values are: Integrity, Focus, and Simplicity.
5+
RustFS is a cutting-edge open-source infrastructure solution for distributed object storage. It is a project driven by a global community of talented storage architects and open-source enthusiasts. Our core values are: Integrity, Focus, and Simplicity.
66

7-
Our vision is to provide multilingual, secure, and cost-effective distributed object storage products to the world.
7+
Our vision is to provide secure, multilingual, and cost-effective distributed object storage solutions to the world.
88

9-
RustFS continuously ensures data security and reduces data storage costs across all aspects including artificial intelligence, big data, video, cloud computing, encrypted storage, industrial production, cloud-native, and data backup.
9+
RustFS continuously ensures data security and reduces storage costs across diverse sectors, including artificial intelligence, big data, media streaming, cloud computing, encrypted storage, industrial IoT, cloud-native applications, and data backup.
1010

11-
Helping humanity achieve global storage solutions, we are on the way...
11+
We are committed to building the future of global storage infrastructure.
1212

1313
## Our Vision and Values
1414

@@ -34,8 +34,9 @@ Integrity, Focus, Simplicity
3434

3535
> According to Fortune Business Insights, the global data storage market is expected to grow from $218.33 billion in 2024 to $774 billion in 2032, with a compound annual growth rate of 17.1% during this period.
3636
37-
### Invest in RustFS
37+
### Investor Relations
3838

39+
For investment opportunities or strategic partnerships, please contact us.
3940

4041
📧 **Contact**
4142
<hello@rustfs.com>

docs/administration/iam/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "RustFS IAM Management"
3-
description: "Detailed explanation of user/user group/policy/AK&SK and other content in RustFS."
3+
description: "Comprehensive guide to Identity and Access Management (IAM), including Users, Groups, Policies, and Access Keys."
44
---
55

66
This chapter includes the following content:

docs/concepts/architecture.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,9 @@ In both distributed and single-machine modes, all read and write operations stri
2121

2222
## Several Important Concepts in RustFS
2323

24-
**Object**: The basic object stored in RustFS, such as files, byte streams, anything...
24+
**Object**: The fundamental unit of storage in RustFS, representing files, byte streams, or any unstructured data.
2525

26-
**Bucket**: A logical space used to store Objects. Data between each Bucket is isolated from each other. For clients, it's equivalent to a top-level folder for storing files.
26+
**Bucket**: A logical container for storing Objects. Data is isolated between Buckets. For clients, it functions similarly to a top-level directory.
2727

2828
**Drive**: The disk that stores data, passed as a parameter when RustFS starts. All object data in RustFS will be stored in Drives.
2929

@@ -39,12 +39,10 @@ Therefore, before designing the architecture and deploying devices, note that:
3939

4040
4. Drives in one Set should be distributed across different nodes as much as possible;
4141

42-
## Special Thanks
42+
## Architectural Design
4343

44-
Traditional distributed storage architectures must have: Master nodes, MetaData nodes, and Data Node nodes. This design pattern makes user deployment very complex. At the same time, without rich distributed storage management experience, once metadata is lost, there is a risk of data loss.
44+
Traditional distributed storage architectures often rely on distinct Master nodes, Metadata nodes, and Data nodes. This complexity can make deployment challenging and introduces single points of failure—if metadata is lost, data integrity is at risk.
4545

46-
All nodes are peer-level nodes, greatly simplifying the architecture design and eliminating concerns about metadata loss. A single command can start the system.
46+
RustFS adopts a decentralized, peer-to-peer architecture where all nodes are equal. This design greatly simplifies deployment and eliminates metadata bottlenecks. A single command is sufficient to start the system.
4747

48-
Without losing elegance, simplicity, and reliability, RustFS adopts the same architectural design as MinIO.
49-
50-
Thanks to MinIO's architectural philosophy, which greatly facilitates global users and promotes the S3 protocol.
48+
RustFS draws inspiration from the elegant and scalable architecture of MinIO, adopting a similar design philosophy that prioritizes simplicity and reliability without compromising on features. We acknowledge MinIO's contribution to promoting the S3 protocol and setting a high standard for object storage architecture.

docs/concepts/comparison.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -14,30 +14,30 @@ description: "Comparison of RustFS with mainstream object storage products"
1414
| File Storage || x | x |
1515
| Architecture | Heavy architecture design | Lightweight architecture design | Lightweight architecture design |
1616
| Community Activity ||||
17-
| License Friendliness | Medium | Poor | Excellent |
18-
| Performance | Performance depends on hardware and configuration | High performance, low latency, suitable for high-speed read/write and large-scale object access | High performance, low latency, suitable for high-speed read/write and large-scale object access |
19-
| File Protocol | Supports S3, RBD, CephFS and other protocols | S3 | S3 |
17+
| License Friendliness | Medium | Restrictive (AGPL) | Excellent (Permissive) |
18+
| Performance | Hardware dependent | High performance, low latency | High performance, low latency |
19+
| File Protocol | S3, RBD, CephFS, etc. | S3 | S3 |
2020
| Ease of Use | Low | High | High |
2121
| Scalability | EB level | EB level | EB level |
22-
| Hardware Requirements | High hardware resource consumption | Medium resource consumption, medium hardware requirements | Low resource consumption, lower hardware requirements |
23-
| Memory Stability | Stable | High jitter under high concurrency | Stable |
22+
| Hardware Requirements | High | Medium | Low |
23+
| Memory Management | Manual | GC-based | Ownership-based (No GC) |
2424
| Scaling | High difficulty | Low difficulty | Low difficulty |
2525
| Rebalancing | High resource consumption | Low resource consumption | Low resource consumption |
2626
| Commercial Support ||||
2727

2828

2929

30-
## Global Object Storage Architecture Schools
30+
## Global Object Storage Architectural Approaches
3131

32-
Currently, distributed object storage products worldwide are mainly divided into two schools:
32+
Currently, distributed object storage products worldwide are mainly divided into two architectural approaches:
3333

34-
1. With metadata center, represented by: Ceph;
34+
1. **Centralized Metadata**: Represented by Ceph.
3535

36-
2. Without metadata center, represented by: RustFS and MinIO.
36+
2. **Decentralized Metadata**: Represented by RustFS and MinIO.
3737

38-
Comparison of advantages and disadvantages with/without metadata center:
38+
Comparison of advantages and disadvantages:
3939

40-
| Feature | With Metadata Center | Without Metadata Center |
40+
| Feature | Centralized Metadata | Decentralized Metadata |
4141
| - | - | - |
4242
| Architecture Characteristics | Dedicated metadata server or center for unified metadata management | Metadata distributed across storage nodes, no dedicated metadata server |
4343
| Metadata Management | Efficient centralized management, fast query and update | Distributed metadata storage, avoiding single-point bottlenecks |
@@ -49,6 +49,6 @@ Comparison of advantages and disadvantages with/without metadata center:
4949

5050
## About Storage Speed
5151

52-
RustFS and MinIO adopt the same design, with overall speed depending on the network and hard disk speed of storage nodes. After evaluation, RustFS can achieve 323 GB/s read speed and 183 GB/s write speed.
52+
RustFS and MinIO share similar design principles, with overall speed largely dependent on network bandwidth and disk I/O. Benchmarks indicate that RustFS can achieve read speeds of up to 323 GB/s and write speeds of 183 GB/s.
5353

54-
It can be said that RustFS and MinIO are the only two distributed object storage products in the world with leading speed. Under the same configuration, their speed far exceeds that of Ceph.
54+
RustFS and MinIO stand out as leaders in high-performance distributed object storage. Under comparable configurations, their throughput significantly exceeds that of traditional architectures like Ceph.

0 commit comments

Comments
 (0)