From 44e14873e095c12817be7dc6721d2a3401cb9130 Mon Sep 17 00:00:00 2001 From: iromli Date: Thu, 7 Nov 2024 23:27:40 +0700 Subject: [PATCH] docs: remove spanner references Signed-off-by: iromli --- docs/janssen-server/install/README.md | 2 +- docs/janssen-server/planning/caching.md | 6 +++--- docs/janssen-server/planning/persistence.md | 4 ---- .../reference/kubernetes/config-secret-keys.md | 2 +- 4 files changed, 5 insertions(+), 9 deletions(-) diff --git a/docs/janssen-server/install/README.md b/docs/janssen-server/install/README.md index 0956db0cf79..fe22ec8619c 100644 --- a/docs/janssen-server/install/README.md +++ b/docs/janssen-server/install/README.md @@ -32,7 +32,7 @@ configuration tool to perform any other last mile configuration. ## Databases The Janssen Project gives you a few options to store data: MySQL, Postgres, -Couchbase, Amazon Aurora, and Spanner. You can also configure an in-memory cache +Couchbase, and Amazon Aurora. You can also configure an in-memory cache server like Redis. Sometimes installation and configuration of this database is included in the setup process. Sometimes, you need to setup the database ahead of time. Please refer to the database instructions specific for your diff --git a/docs/janssen-server/planning/caching.md b/docs/janssen-server/planning/caching.md index bd03ed6f3e1..b4faa5425a0 100644 --- a/docs/janssen-server/planning/caching.md +++ b/docs/janssen-server/planning/caching.md @@ -27,9 +27,9 @@ cluster, it may be convenient to persist the "cache" data in the database. Janssen Auth Server can use "ephemeral buckets", which exist only in memory, for caching. -1. **Redis** The best choice if you need a cache service for RDBMS, -or Spanner. Great performance and low cache miss rate. Commercial Redis -supports TLS, which is a good option if you need secure communication. +1. **Redis** The best choice if you need a cache service for RDBMS. Great performance +and low cache miss rate. Commercial Redis supports TLS, which is a good option if you +need secure communication. 1. **Memcached** Still a good choice, especially if that's what you already run for other applications. We have observed a slightly higher cache miss diff --git a/docs/janssen-server/planning/persistence.md b/docs/janssen-server/planning/persistence.md index 21f7f9bd885..3b206526750 100644 --- a/docs/janssen-server/planning/persistence.md +++ b/docs/janssen-server/planning/persistence.md @@ -48,7 +48,3 @@ The main catch is that write operations are limited to one region, with the ability to failover to another region. But to accomplish this, you need a cloud engineer to implement it. -1. **Spanner** Google's multi-region cloud database as a service, Spanner -was purpose-built for auto-scaling, and multi-region persistence. It has its own -API, although recently Google added support for MySQL and Postgres drivers. - diff --git a/docs/janssen-server/reference/kubernetes/config-secret-keys.md b/docs/janssen-server/reference/kubernetes/config-secret-keys.md index 48395c38ea8..50554b33843 100644 --- a/docs/janssen-server/reference/kubernetes/config-secret-keys.md +++ b/docs/janssen-server/reference/kubernetes/config-secret-keys.md @@ -591,7 +591,7 @@ Note that `_secret` may contain other keys depending on persistence, secrets/con } ``` -1. Persistence is set to `spanner` or secrets/configmaps backend is set to `google`: +1. Secrets/configmaps backend is set to `google`: ```json "_secret": {