Skip to content

Commit

Permalink
Update docs
Browse files Browse the repository at this point in the history
  • Loading branch information
yang-xiaodong committed May 13, 2022
1 parent 6f0901b commit a4450c9
Show file tree
Hide file tree
Showing 2 changed files with 20 additions and 0 deletions.
10 changes: 10 additions & 0 deletions docs/content/user-guide/en/storage/general.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,16 @@ Since Kafka is born with message persistence using files, Kafka will ensure that

## Storage

### Supported storages

CAP supports the following types of transaction-enabled databases for storage:

* [SQL Server](sqlserver.md)
* [MySQL](mysql.md)
* [PostgreSql](postgresql.md)
* [MongoDB](mongodb.md)
* [In-Memory Storage](in-memory-storage.md)

After CAP is started, two tables are generated in used storage, by default the name is `Cap.Published` and `Cap.Received`.

### Storage Data Structure
Expand Down
10 changes: 10 additions & 0 deletions docs/content/user-guide/zh/storage/general.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,16 @@ CAP 需要使用具有持久化功能的存储介质来存储事件消息,例

## 消息存储

### 支持的存储

CAP 支持以下几种具有事务支持的数据库做为存储:

* [SQL Server](sqlserver.md)
* [MySQL](mysql.md)
* [PostgreSql](postgresql.md)
* [MongoDB](mongodb.md)
* [In-Memory Storage](in-memory-storage.md)

在 CAP 启动后,会向持久化介质中生成两个表,默认情况下名称为:`Cap.Published` `Cap.Received`

### 存储格式
Expand Down

0 comments on commit a4450c9

Please sign in to comment.