Published in


A Data Vault Analogy

Born out of a need to model, integrate, and historicize a vast landscape of operational systems around business objects, data vault has grown into two differing philosophies today.

Ensemble Modelling

Data Vault 2.0

The views expressed in this article are based on my own experience. You should test implementation performance before committing to this implementation. The article provides no guarantees in this regard.

Snowflake articles from engineers using Snowflake to power their data.

Recommended from Medium

Python For Beginners: 14 Reasons Why You Should Learn It

How to create a Mixin Bot

The Unique value of Tableau-CRM for Salesforce customers

Laravel Routing — A step up

Key Principles of Software Architecture

Types of Notes in a PKM explained with a Gardening Analogy (Part I)

All you need to know to get started with ETCD in kubernetes.

How to start using the command line (part 2)

BSP how to start using the command line nickang blog

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Patrick Cuba

Patrick Cuba

A Data Vault 2.0 Expert, Snowflake Solution Architect

More from Medium

Data Vault Industry Verticals

The 10 Capabilities of Data Vault 2.0 You Should Be Using

Why are Google BigQuery, Snowflake, Redshift and other cloud data warehouses slower than most…

Modern Data Pipelines with Azure Synapse Analytics and Azure Purview