Problem
Build the connection and history layer for a team-messaging platform organized around workspaces and channels, including channels large enough to hold an entire company. Design it from a blank canvas so a crash between persisting a message and fanning it out can never lose it, the connection layer and the shared routing state every gateway needs hold up independently, losing your single largest connection gateway can't silently drop live sessions, and a channel with tens of thousands of members reading its history can't be served by the same path that absorbs every new message write.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.