Skip to content

Commit 8f8c209

Browse files
authored
Update README.md
1 parent 42013f1 commit 8f8c209

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,11 @@ With its advanced real‑time update capabilities, DynaRust pushes live changes
88

99
---
1010

11+
## 🛜 Main node running:
12+
![main](https://github.com/yourfavDev/DynaRust/blob/42013f18f1f4d0ede1cad81ed1249e42f12f2951/docs/main.png)
13+
## ⏎ Second node joins the main node (forming a cluster)
14+
![second](https://github.com/yourfavDev/DynaRust/blob/42013f18f1f4d0ede1cad81ed1249e42f12f2951/docs/second.png)
15+
1116
## ✨ Key Features
1217

1318
* **🔥 HOT RELOAD & REAL‑TIME UPDATES:**
@@ -16,6 +21,7 @@ With its advanced real‑time update capabilities, DynaRust pushes live changes
1621
# Example: Subscribe to 'statusKey' in the 'notifications' table
1722
curl -N http://localhost:8080/notifications/subscribe/statusKey
1823
```
24+
![liveupdate](https://github.com/yourfavDev/DynaRust/blob/edc84068e9f88be693cdeb7085b19a648ea33b7d/docs/liveupdate.gif)
1925
Changes are pushed instantly (< 5 ms latency). On a standard VPS (1GB RAM, 100Mbps), a single node handles up to **5000 simultaneous live connections** 💪. Need more capacity? Just add more nodes!
2026

2127
* **Use Case Example:** Imagine a web UI needing push notifications. Store device IDs as keys in a `devices` table. Use a separate `status` key in the same table. The frontend listens to `devices/subscribe/status`. The backend iterates through device keys, performs actions, and updates the `status` key, instantly notifying all listening frontends. Simple and blazing fast! ⚡️

0 commit comments

Comments
 (0)