> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/d/data-warehousing.md). # Data Warehousing Electronic storage of a large amount of information by a business, in a manner that is secure, reliable, easy to retrieve, and easy to manage. Data warehousing is the process of collecting, storing, and managing large volumes of structured data from multiple sources in a centralized repository optimized for analysis and reporting. A data warehouse organizes data into schemas and tables designed for fast query performance, typically using a columnar storage format. Data warehouses differ from operational databases in that they are optimized for read-heavy analytical queries rather than transactional workloads. Common data warehouse solutions include Snowflake, Amazon Redshift, Google BigQuery, and Clickhouse. Data is typically loaded into a warehouse through ETL (Extract, Transform, Load) or ELT pipelines. For API management, data warehousing provides a foundation for business intelligence around API usage. Aggregated metrics such as request counts, error rates, latency distributions, and consumer behavior can be queried efficiently. This data helps teams make informed decisions about API versioning, deprecation, capacity planning, and pricing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/d/data-warehousing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.