May 14, 2025 5 min read Data Architecture Series: REFERENCE Home

Reference Data Architecture: Small Data That Keeps Systems Aligned

Reference data is small, but the blast radius is large. A wrong currency, country, tax code, or status value can break integrations and reporting.

I treat reference data as product data because small lookup values can quietly control big business behavior. I recommend versioning, approvals, cached lookup paths, and snapshots for analytics.

Small lists with large consequences

Small lists with large consequences Reference data shown as a four part decision frame. Small lists with large consequences The shape matters because different teams need different proof from the same data. Business moment Currency, tax, country,status, and reason codes Stored shape Allowed value, description, owner,effective dates, and version Decision meaning A shared code that makes systemsbehave consistently Typical handles code description effective_from owner

Reference data looks small until one code changes product behavior, tax reporting, and integration contracts.

How shared codes keep rules aligned

How shared codes keep rules aligned Reference data shown as operating board with inputs and decisions. How shared codes keep rules aligned Daily operating moment Source Tax rule adds a newcategory Data kept Code, label, effectivedates, owner, andapproval Who uses it Apply productrules Validateintegrations Keep reportsaligned Control rollout bydate Reference data looks small until one code changes productbehavior, tax reporting, and integration contracts.

Reference data looks small until one code changes product behavior, tax reporting, and integration contracts.

Typical systems of record

I do not trust a data flow until ownership, freshness, and allowed use are explicit.

PostgreSQL, SQL Server, DynamoDB, Cosmos DB, Redis, object storage with versioned files, warehouses for snapshots.

Provider options in practice

ProviderTypical services
AWSS3 versioning, RDS, DynamoDB, AppConfig, Glue Data Catalog.
AzureApp Configuration, Azure SQL, Cosmos DB, Purview, Synapse.
Google CloudCloud SQL, Firestore, Cloud Storage versioning, Dataplex, BigQuery.

Real company pattern

My recommendation in this reference data pattern is to keep approvals and effective dates visible, because small code changes can quietly change business behavior.

Stripe country and currency style API data is a practical public example: payment platforms expose controlled reference values so integrations do not invent their own country, currency, and capability rules.

Real world operating example

I prefer this kind of example because it forces the design to answer real questions about latency, recovery, and handoffs.

A tax service owns tax category reference data. Checkout validates every item category against the current approved version, while finance reports can still reproduce last quarter using the old version.

Small implementation example

This is the part where theory has to meet the actual work people do every day.

with active_rate as (
  select tax_rate
  from reference.tax_rates
  where country_code = :country_code
    and region_code = :region_code
    and active = true
    and effective_from <= :checkout_time
    and (effective_to is null or effective_to > :checkout_time)
)
select max(tax_rate) as tax_rate,
       case when count(*) = 1 then 'ALLOW_CHECKOUT' else 'BLOCK_CHECKOUT' end as decision
from active_rate;

The query permits checkout only when exactly one active tax rate matches the place and time. Missing or duplicate reference data blocks the transaction.

Operational traps

Where to go next

Written by Arunkumar Ganesan.

What I learnt is that reference data breaks trust when teams assume it is too small to govern.

#DataArchitecture #DataEngineering #ETL #CloudArchitecture #REFERENCE