Open
Description
Just to start a discussion, I guess I want some feedback here as well.
Why not store the data in S3? As far as I can see, the counters are relative costly. Possibly the following would work:
- Store any hit to s3, either find a way to efficiently append to a s3 data struct or throw single hits into one folder. if you take the day, month, year into account, folders can make up for some of the lost features.
- Provide lambda magic to determine if there is data and do the calculations: day, month, year, per site. Remember: The data is write once, so as soon as this is done, its read only. Exception: actual month.
- daily has to be generated each day
- updating the actual months totals sum(days)
- updating yearly totals sum(year)
- maybe a dynamic solution for real time data, a listener for s3 writes will possibly do.
The obvious flaws are missing "Paging" of detail data and large datasets. However, I did not wanted to imply that dynamo is completely off the board, but maybe its a simplification to initially give the data to s3
Metadata
Metadata
Assignees
Labels
No labels