25 lines
1,001 B
Org Mode
25 lines
1,001 B
Org Mode
|
:PROPERTIES:
|
||
|
|
:ID: d07a937b-a722-403c-a165-e2bbe9adcb11
|
||
|
|
:END:
|
||
|
|
#+title: 2021-09-30
|
||
|
|
|
||
|
|
* Talking about analytics reporting and tagging with Gavin
|
||
|
|
|
||
|
|
** Analytics view
|
||
|
|
Long-term goal (since 2014) is to move analytics to be pre-materialized using
|
||
|
|
stream processing.
|
||
|
|
|
||
|
|
The analytics view is intended to be the place a system goes to to retreive the
|
||
|
|
view of analytics it needs (e.g. hundreds of endpoints for specific use cases).
|
||
|
|
|
||
|
|
As a first step, we can set up a service hosting endpoints for our reporting
|
||
|
|
needs, and gradually evolve that into an analytics reporting service with
|
||
|
|
performant materialized views backing it.
|
||
|
|
** Tagging
|
||
|
|
- Campaigns processes one action per subscriber at a time, locking it.
|
||
|
|
- Tagging queues have priorities.
|
||
|
|
- Have tagging operations with multiple tags emit events for each tag in the
|
||
|
|
operation at different priorities, thus spreading out actions applied to a
|
||
|
|
particular subscriber and reducing contention.
|
||
|
|
- Have bulk tagging jobs apply at a different priority?
|