docs: Add Appendix section with questions on event sourcing
This commit is contained in:
parent
2b2c136c67
commit
687cb2cfba
1 changed files with 12 additions and 0 deletions
12
manifesto.md
12
manifesto.md
|
|
@ -151,3 +151,15 @@ The data catalog is an essential component that enables cache-aware planning of
|
|||
## Entity Relationships
|
||||
Note: Data services are missing below. They could be "libraries" for data, e.g. filling an organizational role for data dependencies at a larger scale.
|
||||
|
||||
# Appendix
|
||||
|
||||
## Is this some rotation of event sourcing?
|
||||
|
||||
Event sourcing aspires to be honest about the different real data captured by and internal to the system.
|
||||
|
||||
# Describe event sourcing's worldview/tenets as relevant to databuild AI!
|
||||
|
||||
## Why not data build services?
|
||||
|
||||
Example use case:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue