Skip to content
Tagged articles

ODS

11 articles · Page 1 of 1
Data Practical Notes
Data Practical Notes
Nov 5, 2026 · Big Data

Data Lake vs Data Warehouse: Architecture Differences and Selection Guide

This article explains the core differences between data lakes and data warehouses, detailing their architectures (ODS/DWD/DWS/ADS layers, schema-on-write vs schema-on-read), how they complement each other in a combined architecture, and provides three key questions to guide technology selection based on data types, user roles, and team capacity.

ADSDWDDWS
0 likes · 14 min read
Data Lake vs Data Warehouse: Architecture Differences and Selection Guide
Architects' Tech Alliance
Architects' Tech Alliance
Oct 24, 2026 · Artificial Intelligence

China Mobile's Open Disaggregated Supernode (ODS) Architecture for AI Compute

China Mobile Cloud unveils its Open Disaggregated Supernode (ODS) architecture, addressing five core challenges of traditional AI supernodes — hardware lock-in, proprietary interconnects, power/cooling limits, scale constraints, and maintenance complexity — through hardware disaggregation, open Ethernet/RoCE/FARE protocols, and optical circuit switching, achieving 50-90% power and cost reductions while enabling multi-vendor GPU clusters up to 128 cards per pod.

AI supernodeChina Mobile CloudFARE
0 likes · 6 min read
China Mobile's Open Disaggregated Supernode (ODS) Architecture for AI Compute
Data Integration and Governance
Data Integration and Governance
Apr 30, 2026 · Databases

Clear Differences Between ODS, Data Marts, and Data Warehouses

The article explains how ODS serves as a short‑term, source‑aligned store for near‑real‑time data, Data Marts provide department‑focused, lightly aggregated datasets, and Data Warehouses act as the central, integrated, non‑volatile repository, comparing modeling styles and architectural approaches.

Data MartData ModelingETL
0 likes · 9 min read
Clear Differences Between ODS, Data Marts, and Data Warehouses
Data Integration and Governance
Data Integration and Governance
Mar 6, 2026 · Big Data

Incremental vs Full Data Sync: How to Choose and Implement It

The article explains how to decide between incremental and full data synchronization based on business patterns, describes three table types, outlines critical incremental‑sync details such as checkpointing, transaction integrity, large‑batch handling and log retention, and shows how to merge increments into full snapshots in a data‑warehouse pipeline.

DWDETLIncremental Sync
0 likes · 10 min read
Incremental vs Full Data Sync: How to Choose and Implement It
Smart Sea Tide
Smart Sea Tide
Jan 9, 2026 · Databases

How to Build a Layered Data Warehouse Architecture

The article outlines the essential principles and step‑by‑step design of a three‑layer data warehouse—source (ODS), historical, and data‑model layers—covering data consistency, universality, storage strategies, usability, and security to help architects construct reliable analytical platforms.

Data ConsistencyLayered ArchitectureODS
0 likes · 9 min read
How to Build a Layered Data Warehouse Architecture
Data Practical Notes
Data Practical Notes
Jul 16, 2025 · Databases

Data Warehouse Architecture Explained: 5-Step Guide to Building Your Enterprise Analytics Foundation

This article explains why a data warehouse is the essential foundation for enterprise digital transformation, detailing the differences between databases and data warehouses, the classic ODS/DWD/DWS/ADS layered architecture, and a practical five-step process to build a warehouse from scratch — starting with a core business scenario, ingesting raw data, cleaning and standardizing, building theme-based summary tables, delivering ready-to-use analytics layers, integrating with BI, establishing data standards, and fostering a data-driven culture.

ADSBusiness IntelligenceDWD
0 likes · 15 min read
Data Warehouse Architecture Explained: 5-Step Guide to Building Your Enterprise Analytics Foundation
Didi Tech
Didi Tech
Aug 31, 2023 · Big Data

Data Stability Construction and Fault Governance Practices at Didi Customer Service

Didi’s multi‑year data‑stability program for its customer‑service platform progressed through fault‑centered engineering, business‑aligned cross‑team work, and capability normalization, instituting pre‑, mid‑ and post‑fault safeguards, clear ownership, automated alerts and repair tools, which cut fault count by 42 % and more than doubled mean‑time‑to‑repair while boosting team communication and satisfaction.

Data ReliabilityODSautomation
0 likes · 16 min read
Data Stability Construction and Fault Governance Practices at Didi Customer Service