dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-10 03:45:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update apps/docs/pages/guides/realtime/architecture.mdx

Browse Source 
Co-authored-by: Wen Bo Xie <5532241+w3b6x9@users.noreply.github.com>
This commit is contained in:
Chase GranberryandWen Bo Xie authored and GitHub committed 2023-03-15 07:28:35 -07:00
1 parent 9a07965aab
commit 5f34fb353a
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/pages/guides/realtime/architecture.mdx
+1 -1
View File
@@ -29,7 +29,7 @@ Broadcast lets you send a message from any connected client to a Channel. Any ot
This works globally. A client connected to a Realtime node in the United States can send a message to another client connected to a node in Singapore. Simply connect two clients to the same Realtime Channel and they'll all receive the same messages.
Broadcast is useful for getting messages to users in the same location very quickly. If a group of clients are connected to a node in Singapore, the message only needs to go to that Realtime node in Singapore and back down. If users are close to a Realtime node they'll get Broadcast messages in under 50 milliseconds, basically the time it takes to ping the cluster.
Broadcast is useful for getting messages to users in the same location very quickly. If a group of clients are connected to a node in Singapore, the message only needs to go to that Realtime node in Singapore and back down. If users are close to a Realtime node they'll get Broadcast messages in the time it takes to ping the cluster.
Thanks to the Realtime cluster, you (an amazing Supabase dev) don't have to think about which region your users connect to.