-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add readme to describe different schema options
- Loading branch information
1 parent
d2760b5
commit ccc929e
Showing
1 changed file
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Notifications schemas | ||
|
||
There are three schemas presented here, demonstrating different combinations of options to model this problem. | ||
|
||
There are two relevant dimensions to decide what schema to use: | ||
|
||
- Should we have relationships for subscribers, unsubscribers, or both? | ||
- Should we use relationships per event type or define event type as a caveat? | ||
|
||
| | Relationships per subscriber | Relationships per unsubscriber | Relationships for both unsubscriber & subscriber | | ||
|----------------------------|-------------------------------------|--------------------------------|--------------------------------------------------| | ||
| Event type in relationship | [schema_subscribers][1] | [schema_unsubscribers][3] | No example yet | | ||
| Event type in caveat | [schema_subscribers_event_types][2] | No example yet | | | ||
|
||
[1]: ./schema_subscribers.yaml | ||
[2]: ./schema_subscribers_event_types.yaml | ||
[3]: ./schema_unsubscribers.yaml |