How layeddie/office_server works
Main Components
a. Web Layer (Phoenix):
• LiveView Components (office_live, office_list_live)
• WebSocket Handlers (box_comms, browser_image)
• HTTP Controllers
• Router
b. Core Application Layer:
• Device Management System
• Temperature Monitoring System
• Authentication Service
• PubSub System
• Presence Service
c. Data Layer:
• Postgres Database (implied by the presence of Repo and migrations)
• Schema representations (Devices, Temperatures)
d. External Components:
• Browser Clients
Component Relationships
• Browser Clients → LiveView + WebSocket Connections
• Web Layer → Core Application (bidirectional)
• Core Application → Database Layer (bidirectional)
Special Architectural Elements
Specific architectural patterns:
• PubSub system for real-time updates
• Supervisor tree for monitoring (monitoring_supervisor)
• WebSocket handlers for device communication
• LiveView for real-time UI updates
• Presence tracking for connected devices
Key Features to Emphasize
Create callouts or annotations for:
• Temperature monitoring system
• Device management capabilities
• Real-time data flow
• Authentication system
• Chart generation (vegalite integration)
Technical Details
A technical stack sidebar showing:
• Elixir/Phoenix framework
• Phoenix LiveView
• WebSocket protocols
• Postgres database
• Tailwind CSS (frontend)
Monitoring and alerts
Remember to:
• Keep the main components visually distinct
• Use consistent symbols throughout
• Notes about scalability considerations
• Error handling paths
• Monitoring points
This design should reflect the Elixir/Phoenix architectural patterns while highlighting the specific requirements of an IoT sensor monitoring system.