Architecture Diagram
Core Components
- Pinpoint API
- ModMS
- Redis
- Geos SOLR
- Logging & Observability (Loki + Grafana)
The main HTTP API that powers internal and external consumers.Responsibilities:
- Serves hourly, daily, and time-segment forecasts
- Aggregates data from ModMS and other upstream systems
- Applies overrides and business logic
Data Flow
1
Client Request
A client (apps, website, Qarar, WeatherWatch, media, etc.) sends a request to the Pinpoint API.
2
Location Resolution
Pinpoint resolves the requested location using Geos SOLR and internal location metadata.
3
Model Data Fetch
Pinpoint queries ModMS for the required model fields and time ranges.
4
Overrides & Business Logic
Redis overrides and business rules are applied on top of the raw model data.
5
Response Caching
The response (or intermediate data) is cached in Redis when applicable.
6
Response to Client
Pinpoint returns a JSON response tailored to the client’s needs (hourly, daily, or time-segment forecasts).