# Why You Should Avoid a Canonical Data Model

DevFeed: [Why You Should Avoid a Canonical Data Model](<https://devfeed.tech/articles/why-you-should-avoid-a-canonical-data-model-21255.md>)

Original publisher: [Read original article](<https://juri.dev/blog/2015/08/link-why-avoid-canonical-datamodels/>)

Published: 2015-08-25T00:00:00Z

Content type: opinion

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [data](<https://devfeed.tech/topics/data.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [data](<https://devfeed.tech/tags/data.md>)

## AI overview

The article argues against using a single canonical data model across an application or service landscape. It recommends assigning data responsibility to a service with an API, while allowing other services to maintain convenient copies that stay synchronized with the authoritative source.

## Source excerpt

Lorem ipsum dolor sit amet