How itsswayize/loadshed works
LightSched serves South African load-shedding information through a web frontend backed by separate stage, place-name, and schedule services. The main user flow is browser → web routes → backend REST requests → rendered pages; stage updates also publish asynchronously, while alert messages are consumed by a worker and forwarded as mobile notifications. The graph reflects shown calls and README-documented integrations; some backend details and the alert worker’s internals were not excerpted.
Main entry points: WebService.java Web gateway · StageService.java Stage API · PlaceNameService.java Places API · PlacesCsvParser.java CSV parser
Components 16
Web frontend
- Web gateway
web/src/main/java/wethinkcode/web/WebService.java - HTML templates
web/src/main/resources/templates
Domain services
- Stage API
stage/src/main/java/wethinkcode/stage/StageService.java - Places API
places/src/main/java/wethinkcode/places/PlaceNameService.java - CSV parser
places/src/main/java/wethinkcode/places/PlacesCsvParser.java - Places memory store
places/src/main/java/wethinkcode/places/db/memory/PlacesDb.java - Schedule API
schedule/src/main/java/wethinkcode/schedule/ScheduleService.java
Messaging and alerts
- Topic sender
common/src/main/java/wethinkcode/loadshed/common/mq/MqTopicSender.java - MQ config
common/src/main/java/wethinkcode/loadshed/common/mq/MQ.java - Alert worker
alert/src/main/java/wethinkcode/alert/AlertService.java
Shared data
- Place models
places/src/main/java/wethinkcode/places/model - Schedule DTOs
common/src/main/java/wethinkcode/loadshed/common/transfer - Stage DTO
common/src/main/java/wethinkcode/loadshed/common/transfer/StageDO.java
Other components
- Browser user
- ActiveMQ broker
- ntfy notifications
Connections 17
- Browser user → Web gateway: requests pages
README.md - Web gateway → Stage API: fetches stage
web/src/main/java/wethinkcode/web/WebService.java - Web gateway → Places API: fetches place data
web/src/main/java/wethinkcode/web/WebService.java - Web gateway → Schedule API: fetches schedule
web/src/main/java/wethinkcode/web/WebService.java - Web gateway → HTML templates: renders pages
web/src/main/java/wethinkcode/web/WebService.java - Places API → CSV parser: parses dataset
places/src/main/java/wethinkcode/places/PlaceNameService.java - CSV parser → Places memory store: builds store
places/src/main/java/wethinkcode/places/PlacesCsvParser.java - Places API → Place models: serves place data
places/src/main/java/wethinkcode/places/PlaceNameService.java - Places memory store → Place models: implements model
places/src/main/java/wethinkcode/places/db/memory/PlacesDb.java - Schedule API → Schedule DTOs: returns schedule
schedule/src/main/java/wethinkcode/schedule/ScheduleService.java - Stage API → Stage DTO: reads and returns
stage/src/main/java/wethinkcode/stage/StageService.java - Stage API → Topic sender: publishes updates
stage/src/main/java/wethinkcode/stage/StageService.java - Stage API → ActiveMQ broker: broadcasts stage
README.md - Topic sender → MQ config: uses settings
- Web gateway → ActiveMQ broker: queues alerts
web/src/main/java/wethinkcode/web/WebService.java - ActiveMQ broker → Alert worker: delivers messages
README.md - Alert worker → ntfy notifications: pushes notifications
README.md