Update aspect.md

This commit is contained in:
Mars Lan 2019-12-18 20:39:13 -08:00 committed by GitHub
parent 0ec3cdb64c
commit 8f120f15e3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -11,9 +11,9 @@ It is also possible to apply the retention based on time, e.g. only keeps the me
While a metadata aspect can be arbitrary complex document with multiple levels of nesting, it is sometimes desirable to break a monolithic aspect into smaller independent aspects.
This will provide the benefits of:
1. **Faster read/write**: As metadata aspects are immutable, every `update` will lead to the writing the entire large aspect back to the underlying data store.
1. **Faster read/write**: As metadata aspects are immutable, every "update" will lead to the writing the entire large aspect back to the underlying data store.
Likewise, readers will need to retrieve the entire aspect even if its only interested in a small part of it.
2. **Ability to independently version different aspects**: For example, one may like to get the change history of all the `ownership metadata` independent of the changes made to `schema metadata` for a dataset.
2. **Ability to independently version different aspects**: For example, one may like to get the change history of all the "ownership metadata" independent of the changes made to "schema metadata" for a dataset.
3. **Help with rest.li endpoint modeling**: While its not required to have 1:1 mapping between rest.li endpoints and metadata aspects,
itd follow this pattern naturally, which means one will end up with smaller, more modular, endpoints instead of giant ones.
@ -48,4 +48,4 @@ The [relationship](relationship.md) section explains how this relationship can b
}
]
}
```
```