# Architecture WeatherLayers Cloud is a caching proxy with no periodic preloading. When any user accesses a file for the first time, this when the file is downloaded from the upstream data source, processed and cached. Each such first request is expected to take a longer time to finish, depending on the upstream data source response time. All subsequent requests for the same file are served from the cache, either WeatherLayers internal cache or Cloudflare. This optimises for common usage pattern of users who access the current files or closer forecast offsets over further future forecast offsets. WeatherLayers Cloud doesn’t support an automated scripted usage requesting all forecast offsets upfront on a periodical schedule. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.weatherlayers.com/weatherlayers-cloud/architecture.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.