How dannybrian/eventpresent works
Client-Side Applications (Frontend Layer)
a. Audience App (web/)
b. Big Screen Presentation (web/big/)
c. Admin/Speaker App (web/admin/)
• That all use Paho MQTT client for WebSocket communication
Network Layer
• It handling:
a. Static asset serving
b. WebSocket/MQTT reverse proxy
Message Broker
• Mosquitto MQTT broker as a central component
• Authentication boundaries (adminapp, adminred, big users)
• Connection limits notation
Backend Processing
• Node-RED as the business logic layer
• Flows for message routing and processing
• It to Mosquitto broker
Connection Flow:
Message routing paths between components
• Admin → Mosquitto → Node-RED → Audience/Big Screen
• Audience → Mosquitto → Node-RED → Admin
Authentication Boundaries:
• An authentication zone around admin components
• Password-protected paths
• Anonymous audience access paths
Specific Implementation Details to Note:
Use clear spacing between components
Additional Considerations:
• Scaling notes (file limits for thousands of users)
• Session management (localStorage)
• Build/deployment paths
• SSL toggle points
• Blue: Client applications
• Green: Gateway/Nginx
• Red: Authentication boundaries
• Purple: Message broker
• Orange: Backend processing
• Gray: Infrastructure components
Remember to include a note about the intentionally permissive nature of the system regarding user sessions and anonymous access, as this is a key architectural decision that affects the overall design.