Improve sequence diagram to illustrate restore

maxpert · Dec 6, 2023 · 75a99b1 · 75a99b1
1 parent 5da5e64
commit 75a99b1
Showing 1 changed file with 6 additions and 6 deletions.
diff --git a/docs/src/pages/internals.mdx b/docs/src/pages/internals.mdx
@@ -9,9 +9,12 @@ sequenceDiagram
     main->>+db: OpenStreamDB
     main->>+snapshot: NewSnapshotStorage
     main->>+logstream: NewReplicator
+    opt
+      main->>+snapshot: RestoreSnapshot
+    end
     onTableChanged->>+logstream: Publish 
     onChangeEvent->>+db: Replicate   
-    loop Every minute
+    loop
         main->>+db: CleanupChangeLogs
         main->>+snapshot: SaveSnapshot
     end
@@ -81,11 +84,8 @@ case a node coming back up can be lagging so far behind that `max-log-entries` m
 fully play all logs and restore the state of database. In that case it required that a node restores a
 snapshot and apply current log entries to be fully up-to-date.
 
-As of `v0.6.0+` Marmot supports taking snapshot and being able to fully restore it via
-[NATS Object Storage](https://docs.nats.io/using-nats/developer/develop_jetstream/object).
-
- > In future Marmot plans to support more storage mechanisms like S3 (and compatible APIs including BlackBlaze
- > and Minio), Azure Blob, and SFTP.
+Marmot supports taking snapshot and being able to fully restore it via
+[NATS Object Storage](https://docs.nats.io/using-nats/developer/develop_jetstream/object), S3 (and compatible APIs including BlackBlaze and Minio), Azure Blob, and SFTP.
 
 ### Saving Snapshot
 Everytime a node publishes a new change log to NATs, it saves sequence number of the entry in JetStream. The saved