This website uses cookies. By continuing to browse the site, you confirm your consent to the use of these files.

Data warehouse (DWH)

Infrastructure

A data warehouse (Data Warehouse) is a centralized system for collecting, storing and analyzing large volumes of structured data from various sources to support decision-making.

A data warehouse (Data Warehouse, DWH) is a specialized database or information system designed for centralized collection, integration, cleaning, storage and analysis of large volumes of historical data from many heterogeneous sources (OLTP transactional systems, CRM, ERP, HRM, external sources, web analytics, mobile applications). Unlike operational databases optimized for fast writing and updating of individual records (OLTP — Online Transaction Processing), a data warehouse is optimized for complex analytical queries (OLAP — Online Analytical Processing) that are executed over large volumes of historical data, often with aggregations, groupings and joins of many tables. The key characteristics of a data warehouse according to Inmon: subject orientation (data is organized by subject areas, not by applications), integration (data from different sources is brought to a unified format, codes and units of measurement), non-volatility (data after loading does not change — only new slices are added) and chronology support (the history of changes for the entire period is preserved). The scaling technology plays a key role in the design of modern data warehouses, allowing scaling of capacity and performance as the volume of information grows.

DWH (data warehouse) architecture: layers and ETL Four-layer DWH architecture: data sources (DBMS, files, APIs), ETL (extract, transform, load), warehouse core (Stage, ODS, Core, Data Marts) and access layer (BI tools: Tableau, Power BI, Yandex DataLens). Data warehouse (DWH) — Architecture layers Centralized system for analyzing large volumes of historical data Collect from sources → Clean and transform → Store → Analyze Layer 1: Data sources Relational DBMS Postgres Pro, Oracle, MS SQL MySQL, PostgreSQL Files and logs CSV, Excel, JSON, XML Application and system logs API and streaming data CRM, ERP, web analytics Apache Kafka, Amazon Kinesis Layer 2: ETL/ELT (Cleaning and transformation) ETL tools: Apache Airflow, Talend, Informatica, Pentaho, SSIS, dbt Extract → Transform → Load Layer 3: Warehouse core Stage (raw data) Data unchanged from sources ODS (operational) Cleaned data without transformation Core (hub) Normalized data model Data Marts (showcases) Data for specific business tasks Layer 4: Access and analytics (BI) BI tools: Tableau, Power BI, Yandex DataLens, QlikView Reports | Dashboards | Predictive analytics | Ad-hoc queries DWH — the foundation for data-driven decisions and digital business transformation
Data warehouse (DWH) — term diagram

Architecture and components of a data warehouse

The classic architecture of a data warehouse includes several levels. The data source layer (Source Layer): relational DBMS (Postgres Pro, Oracle, MS SQL), flat files (CSV, Excel, JSON, XML), streaming data (Kafka, Kinesis), APIs of external systems (REST, SOAP), web scraping and mobile SDKs. The ETL/ELT level (Extract, Transform, Load / Extract, Load, Transform): tools for extracting, cleaning, transforming, enriching and loading data into the warehouse (Apache Airflow, Talend, Pentaho, Informatica, SSIS, dbt). The warehouse core level: the Stage zone (raw, untransformed data in the original format), the ODS zone (Operational Data Store — an operational storage for fresh data), the Core zone (the core — a normalized or dimensional data model: Data Vault 2.0, 3NF, Inmon, Kimball), the Data Marts zone (data marts — subsets of data optimized for specific business tasks: finance, sales, procurement, marketing, HR). The access level (Access/Consumption Layer): business intelligence tools (BI: Tableau, Power BI, Qlik, Yandex DataLens, Luxms BI), report building, dashboards, ad-hoc queries (SQL), predictive analytics (Python/R, machine learning). Modern data warehouses are increasingly built using the Lakehouse concept, which combines the flexibility of data lakes (Data Lake) for storing unstructured and semi-structured data and the power of structured warehouses with ACID transactions.

Data warehouse construction methodologies

There are various DWH construction methodologies. The Kimball model (Ralph Kimball, dimensional modeling): building data marts for individual business processes using a "star" schema (star schema: a fact table + dimension tables) or a "snowflake" schema (snowflake schema). Advantages: fast development, comprehensibility for business users, high query performance. The Inmon model (Bill Inmon, Corporate Information Factory — CIF): starts with building a normalized corporate warehouse (Enterprise DWH, 3NF), on the basis of which data marts are then built by subject areas. Advantages: a single source of truth, no data duplication. The Data Vault model (Dan Linstedt): a hybrid approach with the division of entities into Hub (business keys), Link (connections between keys) and Satellite (attributes and context). Advantages: high flexibility to source changes, full traceability of data lineage, parallel loading. The choice of methodology depends on business requirements, source complexity, available team competencies and the project budget. For Russian companies working with state information systems, an important requirement is compliance with personal data legislation and the requirement to store data on the territory of the Russian Federation.

Business value of a data warehouse

A data warehouse is the foundation for corporate analytics and data-driven decision making. Without a high-quality DWH, it is impossible to build reliable and timely reports, predictive models and dashboards for management. The implementation of a DWH allows a company to move from reactive management based on intuition and belated reports to proactive management based on the analysis of historical data and trend identification. The ROI from a DWH implementation can reach hundreds of percent by identifying hidden efficiency reserves, optimizing the assortment, reducing inventory, improving customer service, detecting fraudulent operations and optimizing marketing campaigns. Modern BI tools connect to the data warehouse, providing business users with the ability to independently (self-service BI) build dashboards and reports without the participation of IT specialists. The specialists of the Fintech company have experience in building data warehouses of varying complexity, ensuring high performance, reliability, scalability and full compliance with regulatory requirements.

Frequently asked questions

How is a data warehouse cleaned?

In a data warehouse context, cleaning means data quality processes: deduplication, normalization, removing incorrect or outdated records, and setting up retention policies. This is performed during ETL/ELT stages. In the context of this topic, it is useful to study Hypervisor, the scaling technology and Backup system (SRK).

Where to find data warehouse data?

Data warehouse data is located in specialized storage systems and servers in a data center. Access is provided through BI tools, SQL queries and analytical interfaces. For in-depth study, refer to the sections Workstation and SMEV.

What is a data warehouse called?

A data warehouse (Data Warehouse, DWH) is a centralized database for storing and analyzing information from different sources: ERP, CRM, web services, Excel files and databases. Read more about related aspects in the materials: Containerization (Docker) and Server virtualization.

How is a data warehouse built?

Building a data warehouse includes the following steps: 1) identifying data sources and requirements; 2) designing the data model (star schema, Data Vault, 3NF); 3) setting up ETL/ELT processes; 4) loading historical data; 5) connecting BI tools. More detailed information is available in the articles about Containerization (Docker), Server virtualization and Hypervisor.

What to do if the data warehouse is full?

If the warehouse capacity is exhausted, options include archiving old data, increasing storage capacity using the scaling technology, optimizing data models and setting data retention policies. We also recommend familiarizing yourself with Postgres Pro, data center (DPC) and SMEV for a complete understanding of the topic.

What is the difference between a data warehouse and a regular database?

A regular database (OLTP) is optimized for fast recording and updating of operational data, while a data warehouse (OLAP) is optimized for analyzing large volumes of historical data with complex queries. Here are 5 key differences: purpose, data structure, query type, history storage and load profile. We also recommend familiarizing yourself with Hypervisor, Workstation and the scaling technology for a complete understanding of the topic.

How to open access to a data warehouse?

To provide access to a data warehouse, it is necessary to configure accounts, access rights and roles, connect BI tools and set up security policies. We also recommend familiarizing yourself with SMEV, Hypervisor and SAN (storage area network) for a complete understanding of the topic.

Was this information helpful?

Build reliable IT infrastructure

Build a modern, fault-tolerant IT infrastructure. Design, equipment supply, installation and maintenance turnkey.

Guaranteed result
Selection for your budget
Comprehensive approach
Certified experts

Or contact us:

+7 (499) 238-01-32 sales@fintech.ru

Open from 9:00 am to 6:00 pm