pyers/prsm
1
0
Fork 0
mirror of https://github.com/nvms/prsm.git synced 2025-12-16 00:00:52 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

README

Browse Source
This commit is contained in:
nvms 2025-04-18 11:34:14 -04:00
parent 9c1370dcbf
commit f2b80feab8
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
packages/mesh/README.md
View File

@ -70,23 +70,23 @@ console.log(response); // "echo: Hello!"
Mesh supports multiple real-time patterns—choose where to go next based on your use case: Mesh supports multiple real-time patterns—choose where to go next based on your use case:
- **Pub/Sub messaging (e.g. chat, notifications):** - **Pub/Sub messaging (e.g. chat, notifications):**
→ [Redis Channel Subscriptions](#redis-channel-subscriptions) → [Redis channel subscriptions](#redis-channel-subscriptions)
- **Granular, versioned data sync (e.g. user profiles, dashboards):** - **Granular, versioned data sync (e.g. user profiles, dashboards):**
→ [Record Subscriptions](#record-subscriptions) → [Record subscriptions](#record-subscriptions)
- **Identify users, store connection info, or manage rooms:** - **Identify users, store connection info, or manage rooms:**
→ [Metadata](#metadata) and [Room Metadata](#room-metadata) → [Metadata](#metadata) and [Room metadata](#room-metadata)
- **Control access or validate inputs across commands:** - **Control access or validate inputs across commands:**
→ [Command Middleware](#command-middleware) → [Command middleware](#command-middleware)
Want to see how messages flow across servers? Want to see how messages flow across servers?
→ [Distributed Messaging Architecture](#distributed-messaging-architecture) → [Distributed messaging architecture](#distributed-messaging-architecture)
## Who is this for? ## Who is this for?
The 95% of real-world apps that need real-time sync but don't want to build their own protocol, state engine, or distributed infrastructure. If you're building something that fits into one of the categories below, then this should be a good fit: The 95% of real-world apps that need real-time sync—but don't want to build their own protocol, state engine, or distributed infrastructure. If you're building something like the examples below, Mesh is probably a great fit:
**Collaborative apps** **Collaborative apps**
- Live cursors - Live cursors
@ -106,7 +106,7 @@ The 95% of real-world apps that need real-time sync but don't want to build thei
**Turn-based or async games** **Turn-based or async games**
- Multiplayer puzzles - Multiplayer puzzles
- Card games - Card games
- Structured multiplayer game state (e.g. inventories, turns, positions, shared resources, etc.) - Structured multiplayer game state (e.g. inventories, turns, positions, shared resources)
## Distributed messaging architecture ## Distributed messaging architecture