# Enterprise data and product data: shared technology, different contracts

**NR-006** · Comparison model · v1.0.0 · Reference / illustrative

Two data-platform operating models can use the same engine while requiring different data contracts, workloads, release expectations and ownership.

![Enterprise data and product data: shared technology, different contracts](diagram.svg)

## Architecture problem
Copying a SaaS product telemetry architecture into enterprise finance analytics—or vice versa—creates mismatched reliability, governance and change models.

## Apply when
- Designing one platform for both enterprise insight and embedded product experiences
- Separating SLA, tenancy and ownership responsibilities
- Assessing reuse versus isolation of compute, storage and governance

## Not intended for
- Assuming the data platforms must be fully separate physically
- Assuming shared Databricks or Snowflake implies one architecture
- Ignoring mixed workloads and legitimate overlap

## Design rules
1. Classify every data product by consumer and quality-of-service contract.
2. Enterprise data prioritizes reconciliation, enterprise definitions and auditability.
3. Product data may require tenant isolation, low latency and release alignment.
4. Share tooling deliberately; separate contracts, ownership and SLOs where necessary.
5. Physical consolidation is a decision, not an architectural goal.

## Trade-offs
- Shared infrastructure lowers some platform cost but increases noisy-neighbor and release coupling risks.
- Separate environments simplify isolation but duplicate capabilities.
- Faster product iteration can conflict with stable finance reporting definitions.

## Review questions
- Is consumption analytical, operational, embedded or regulatory?
- What is the tenant isolation model?
- How do product deployments change data contracts?
- Are definitions centrally agreed or product-contextual?

## Download / adapt
- `diagram.drawio` — primary editable diagrams.net file
- `diagram.dot` — independent Graphviz concept source
- `diagram.mmd` — editable Mermaid interpretation
- `diagram.svg` — scalable figure
- `diagram.png` — high-resolution figure
- `metadata.yaml` — structured pattern description

**Reuse:** CC BY 4.0; credit nishtnr, link the license, and indicate changes. Conceptual reference only.