24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
## MODIFIED Requirements
|
|
|
|
### Requirement: Refresh and caching
|
|
The system MUST cache the latest successful ingestion output and MUST serve the cached data to the site renderer.
|
|
|
|
The system MUST support periodic refresh on a schedule (at minimum daily) and MUST support a manual refresh trigger.
|
|
|
|
On ingestion failure, the system MUST continue serving the most recent cached data.
|
|
|
|
The ingestion pipeline MUST use the cache layer (when configured and reachable) to reduce repeated network and parsing work for external sources (for example, YouTube API/RSS and podcast RSS).
|
|
|
|
#### Scenario: Scheduled refresh fails
|
|
- **WHEN** a scheduled refresh run fails to fetch one or more sources
|
|
- **THEN** the site continues to use the most recent successfully cached dataset
|
|
|
|
#### Scenario: Manual refresh requested
|
|
- **WHEN** a manual refresh is triggered
|
|
- **THEN** the system attempts ingestion immediately and updates the cache if ingestion succeeds
|
|
|
|
#### Scenario: Cache hit avoids refetch
|
|
- **WHEN** a refresh run is executed within the cache TTL for a given source+parameters
|
|
- **THEN** the ingestion pipeline uses cached data for that source instead of refetching over the network
|
|
|