Place common modeling situations into a 2x2 based on write volatility and analytic serving needs.
Analytic serving need Low High Write volatility / integrity pressure Normalize High write pressure · Low serving need Core operational entities with frequent updates belong here. Protect integrity first. Split layers High write pressure · High serving need Keep a normalized source or core model, then publish dimensional serving tables downstream. Keep simple Low write pressure · Low serving need A lightweight design may be enough when the dataset is small and rarely used. Denormalize for serving Low write pressure · High serving need Flatten descriptive context into dimensions and facts when the dominant workload is analysis.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in