[ABTEST-132] Group up user timeline events and send them in a batch Created: 07/Jan/20 Updated: 26/Aug/22 |
|
| Status: | Open |
| Project: | A/B Testing |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Epic Link: | ABn Later | ||||||||
| Team: | |||||||||
| Description |
|
Currently, we send events on every request to the public instance meaning that one user visiting a page creates an event and that is being sent right away to the external storage. However, those events can generate a lot of cost and we have the potential to send them in a batch. The external storage system we use (S3), charges us by the size of the data and per request meaning that if we manage to group those events together and send them in a batch, we have a lot of potential to reduce the cost of the system.
AC
|