Skip to content

Commit bb8931b

Browse files
authored
Merge pull request recodehive#1464 from Adez017/dicord
image fix for medallion architecture
2 parents affdc43 + e80fd20 commit bb8931b

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

blog/medallion-architecture/index.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The architecture divides your data journey into three layers:
6161
6262
Each layer has one job. Each layer makes the data a little more trustworthy. By the time data reaches the end, it's reliable, consistent, and ready to power real business decisions.
6363

64-
<!-- ![Three-layer Medallion Architecture flow diagram](./img/medallion-architecture-flow.png) -->
64+
![Three-layer Medallion Architecture flow diagram](./Img/medallion-architecture-flow.png)
6565

6666

6767
## 🥉 Bronze: The "Keep Everything" Layer
@@ -121,6 +121,7 @@ Most of the heavy lifting in a data pipeline lives here. It's not glamorous work
121121
### What Silver looks like in practice
122122

123123
Here's a simple PySpark transformation from Bronze to Silver:
124+
- [Reference code](https://oneuptime.com/blog/post/2026-02-17-how-to-build-a-data-lakehouse-architecture-on-gcp-using-cloud-storage-dataproc-and-bigquery/view)
124125

125126
```python
126127
from pyspark.sql import SparkSession
@@ -276,7 +277,7 @@ In practice, teams often extend the model:
276277
- **Feature layer** — prepared datasets for ML model training, maintained by data science teams on top of Silver
277278
- **Semantic layer** — business-friendly models sitting between Gold and end users for self-serve BI
278279

279-
<!--![Extended Medallion Architecture with optional Landing, Feature, and Semantic layers](./img/medallion-extended-layers.png) -->
280+
![Extended Medallion Architecture with optional Landing, Feature, and Semantic layers](./Img/medallion-extended-layers.png)
280281

281282
The three-tier model is a starting point, not a ceiling. The right number of layers is whatever your team actually needs.
282283

@@ -330,6 +331,7 @@ This is the exact structure we adopted after the revenue incident. Bronze preser
330331
- [RecodeHive - Lakehouse vs Data Warehouse](https://www.recodehive.com/blog/lakehouse-vs-warehouse)
331332
- [RecodeHive - Microsoft Fabric: One Platform, One Lake](https://www.recodehive.com/blog/microsoft-fabric-explained)
332333
- [RecodeHive - Azure Storage & ADLS Gen2](https://www.recodehive.com/blog/azure-storage-options)
334+
- [OneUptime - Build a Data Lakehouse on GCP](https://oneuptime.com/blog/post/2026-02-17-how-to-build-a-data-lakehouse-architecture-on-gcp-using-cloud-storage-dataproc-and-bigquery/view)
333335

334336
## About the Author
335337

0 commit comments

Comments
 (0)