Skip to content

Commit d426911

Browse files
committed
replace proton arch svg to gif
1 parent e9e6c50 commit d426911

File tree

3 files changed

+6
-10
lines changed

3 files changed

+6
-10
lines changed

docs/proton-architecture.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,24 +2,24 @@
22

33
## High Level Architecture
44

5-
The following diagram depicts the high level architecture of Proton.
5+
The following diagram depicts the high level architecture of Proton.
66

7-
![Proton Architecture](/img/proton-high-level-arch.svg)
7+
![Proton Architecture](/img/proton-high-level-arch.gif)
88

99
All of the components / functionalities are built into one single binary.
1010

1111
## Data Storage
1212

13-
Users can create a stream by using `CREATE STREAM ...` [DDL SQL](/proton-create-stream). Every stream has 2 parts at storage layer by default:
13+
Users can create a stream by using `CREATE STREAM ...` [DDL SQL](/proton-create-stream). Every stream has 2 parts at storage layer by default:
1414

15-
1. the real-time streaming data part, backed by Timeplus NativeLog
16-
2. the historical data part, backed by ClickHouse historical data store.
15+
1. the real-time streaming data part, backed by Timeplus NativeLog
16+
2. the historical data part, backed by ClickHouse historical data store.
1717

1818
Fundamentally, a stream in Proton is a regular database table with a replicated Write-Ahead-Log (WAL) in front but is streaming queryable.
1919

2020
## Data Ingestion
2121

22-
When users `INSERT INTO ...` data to Proton, the data always first lands in NativeLog which is immediately queryable. Since NativeLog is in essence a replicated Write-Ahead-Log (WAL) and is append-only, it can support high frequent, low latency and large concurrent data ingestion work loads.
22+
When users `INSERT INTO ...` data to Proton, the data always first lands in NativeLog which is immediately queryable. Since NativeLog is in essence a replicated Write-Ahead-Log (WAL) and is append-only, it can support high frequent, low latency and large concurrent data ingestion work loads.
2323

2424
In background, there is a separate thread tailing the delta data from NativeLog and commits the data in bigger batch to the historical data store. Since Proton leverages ClickHouse for the historical part, its historical query processing is blazing fast as well.
2525

static/img/proton-high-level-arch.gif

418 KB
Loading

static/img/proton-high-level-arch.svg

Lines changed: 0 additions & 4 deletions
This file was deleted.

0 commit comments

Comments
 (0)