eliott/Olares
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rebrand docs content for beOS Pro

Browse Source
This commit is contained in:
Eliott van Nuffel
2026-03-09 10:19:35 +01:00
parent 150f4a8ef4
commit d4e933688d
616 changed files with 6294 additions and 6294 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/developer/develop/advanced/database.md
View File

@@ -1,6 +1,6 @@
# Database
The Olares system provides three most popular data storage cluster for all APPs, covering `RDS`, `NoSQL`, and `Cache` data storage use cases.
The beOS Pro system provides three most popular data storage cluster for all APPs, covering `RDS`, `NoSQL`, and `Cache` data storage use cases.
## RDS
@@ -9,7 +9,7 @@ The system has deployed **PostgreSQL** and provides two types of databases.
- **Standalone PostgreSQL**, providing the most commonly used `RDS` database layer functions.
- **Distributed PostgreSQL** extension, powered by **Citus**. Provides the ability to horizontally scale the database.
When setting up a **PostgreSQL** database, you can specify the type of database to be used in [OlaresManifest.yaml](../package/manifest.md#middleware).
When setting up a **PostgreSQL** database, you can specify the type of database to be used in [beOS ProManifest.yaml](../package/manifest.md#middleware).
```yaml
middleware:
@@ -20,13 +20,13 @@ postgres:
distributed: true # Whether the database is distributed in the cluster.
```
If you use **Citus**, **Olares** will automatically shard the database tables and perform rebalancing during the horizontal scaling of **PostgreSQL** replicas.
If you use **Citus**, **beOS Pro** will automatically shard the database tables and perform rebalancing during the horizontal scaling of **PostgreSQL** replicas.
## NoSQL
The NoSQL cluster is not deployed by default in Olares, but it can be easily installed from the Market. To set up a NoSQL cluster, the administrator needs to install the [**MongoDB**](https://market.olares.com/middleware/mongodb) middleware. Once installed, the [Percona Operator for MongoDB](https://github.com/percona/percona-server-mongodb-operator) automatically manages the **MongoDB** cluster. Users can then horizontally scale **MongoDB** cluster replicas, as well as perform backup and restore operations on databases.
The NoSQL cluster is not deployed by default in beOS Pro, but it can be easily installed from the Market. To set up a NoSQL cluster, the administrator needs to install the [**MongoDB**](https://market.beos.local/middleware/mongodb) middleware. Once installed, the [Percona Operator for MongoDB](https://github.com/percona/percona-server-mongodb-operator) automatically manages the **MongoDB** cluster. Users can then horizontally scale **MongoDB** cluster replicas, as well as perform backup and restore operations on databases.
You can specify detailed configuration for MongoDB in [OlaresManifest.yaml](../package/manifest.md#middleware) as follows:
You can specify detailed configuration for MongoDB in [beOS ProManifest.yaml](../package/manifest.md#middleware) as follows:
```yaml
middleware:
@@ -47,9 +47,9 @@ options:
## Cache
In terms of the Cache cluster, Olares uses Redis Cluster. The cluster is managed by a customized [Redis Cluster Operator](https://github.com/beclab/redis-cluster-operator) to achieve cloud nativeness. It enables us to scale replicas horizontally in a convenient and effective manner.
In terms of the Cache cluster, beOS Pro uses Redis Cluster. The cluster is managed by a customized [Redis Cluster Operator](https://github.com/beclab/redis-cluster-operator) to achieve cloud nativeness. It enables us to scale replicas horizontally in a convenient and effective manner.
To ensure **data isolation** between users and apps in the **Redis cluster**, the **Olares** system has added a **Redis cluster proxy**. It isolates data based on the `namespace`. This operation is transparent, meaning app developers typically do not need to be aware of it.
To ensure **data isolation** between users and apps in the **Redis cluster**, the **beOS Pro** system has added a **Redis cluster proxy**. It isolates data based on the `namespace`. This operation is transparent, meaning app developers typically do not need to be aware of it.
Additionally, this proxy simplifies the process of connecting to clusters. It eliminates the need to switch from a **standalone Redis Client** to a **Redis Cluster client** in the app, thus simplifying app code modifications.
@@ -61,5 +61,5 @@ middleware:
```
:::info NOTE
Since Olares uses the Redis Cluster version, developers need to understand the usage restrictions of Redis Cluster in detail when using it.
Since beOS Pro uses the Redis Cluster version, developers need to understand the usage restrictions of Redis Cluster in detail when using it.
:::