From bf053386a44c4f3b302a1915adb988be9a026ad6 Mon Sep 17 00:00:00 2001 From: Feng Ruohang Date: Wed, 16 Sep 2026 18:26:03 +0800 Subject: [PATCH] docs: link compression and federation to maintained design records Signed-off-by: Feng Ruohang --- docs/compression/README.md | 2 ++ docs/federation/lookup/README.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/docs/compression/README.md b/docs/compression/README.md index 1c6194031..51acaa2a5 100644 --- a/docs/compression/README.md +++ b/docs/compression/README.md @@ -1,5 +1,7 @@ # Compression Guide +For SILO's current SSE-C compression and historical-object boundary, see the [maintained encryption guide](https://silo.pgsty.com/administration/server-side-encryption/server-side-encryption-sse-c/) and [SSE-C replica design](https://silo.pgsty.com/blog/design/ssec-replica-integrity/). Check the documented release boundary before applying main-branch behavior to an older binary. + Silo server allows streaming compression to ensure efficient disk space usage. Compression happens inflight, i.e objects are compressed before being written to disk(s). Silo uses [`klauspost/compress/s2`](https://github.com/klauspost/compress/tree/master/s2) diff --git a/docs/federation/lookup/README.md b/docs/federation/lookup/README.md index d76497234..b57338171 100644 --- a/docs/federation/lookup/README.md +++ b/docs/federation/lookup/README.md @@ -1,5 +1,7 @@ # Federation Quickstart Guide *Federation feature is deprecated and should be avoided for future deployments* +The maintained [federated CopyObject design](https://silo.pgsty.com/blog/design/federated-copy-object/) records the destination encryption, checksum, Object Lock and committed-response contract, including its Server release boundary. + This document explains how to configure Silo with `Bucket lookup from DNS` style federation. ## Cross-deployment copy behavior