minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-04-22 19:02:57 +03:00
Code

Add Multipart to Concepts and Glossary (#609)

Browse Source 
Closes #595 

Applies multipart feedback in comments of PR #588.
This commit is contained in:
Daryl White 2022-10-18 13:25:50 -05:00 committed by GitHub
parent b88a29a223
commit 0aa9ee7e2b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
source/glossary.rst
View File

@ -150,6 +150,15 @@ Glossary
A system :term:`topology` that uses more than one server and more than one drive per server to host a MinIO instance.
MinIO recommends Kubernetes for distributed deployments.
multipart upload
Multipart upload is a client-initiated :s3-docs:`S3 function <mpuoverview.html>` that splits a single object into multiple parts for moving from one location to another.
The client uploads each part independently to MinIO, and MinIO manages reconstructing those received parts into the original object.
Multipart uploads provide benefits such as improved throughput and resiliency to network errors.
Use multipart uploads for objects greater than 100MB in actual or estimated size for best results.
See :s3-docs:`Amazon AWS documentation <mpuoverview.html>` for more details.
network encryption
A method of securing data during transit from one location to another, such as server-server or client-server.
MinIO supports :ref:`Transport Layer Security (TLS) <minio-tls>`, version 1.2 and later, for both incoming and outgoing traffic.

9
source/operations/concepts.rst
View File

@ -126,6 +126,15 @@ There are several options to manage your MinIO deployments and clusters:
- The :ref:`MinIO Console <minio-console>` graphical user interface for individual instances
- In Kubernetes, with the :ref:`MinIO Operator Console <minio-operator-console>`
How do I upload objects to MinIO?
---------------------------------
You can use any S3-compatible SDK to upload objects to a MinIO deployment.
Each SDK performs the equivalent of a PUT operation which transmits the object to MinIO for storage.
MinIO also implements support for :s3-docs:`multipart uploads <mpuoverview.html>`, where clients can split an object into multiple parts for better throughput and reliability of transmission.
MinIO reassembles these parts until it has a completed object, then stores that object at the specified path.
How does MinIO provide availability, redundancy, and reliability?
-----------------------------------------------------------------