Uploaded Content: Difference between revisions
Created page with "This page contains notes on allowed content uploads to GoalStriving. This will likely become the most expensive resource constraint as we scale. Once we allow people to have a certain amount of disk space, taking it away (after they have used it) is nearly impossible. === Options === These are options to consider for storage. # Centrally managed AWS S3 bucket for each user # Users can manage their own AWS S3 bucket # Users use their own Google Drive, OneDrive, Box.co..." |
No edit summary |
||
| Line 28: | Line 28: | ||
* We offer 10GB per user | * We offer 10GB per user | ||
* If we have 1,000 users and each are using half of their storage, we would only be paying $115 per month in storage. | * If we have 1,000 users and each are using half of their storage, we would only be paying $115 per month in storage. | ||
=== Data Transfer Costs === | |||
At scale, I would be at least as concerned about data transfer and request costs as storage. If someone stores a 100 MB video and watches it repeatedly, storing it costs only about: $0.0023/month. The bandwidth involved in repeatedly delivering that video could cost considerably more. | |||
AWS specifically breaks S3 pricing into storage, requests/retrieval, data transfer, management and other components. Data transfer between S3 and AWS services in the same region can be free under applicable conditions, while internet delivery has separate pricing considerations. | |||
For WikiFam, I'd therefore design around CloudFront in front of S3, rather than having browsers continually retrieve objects directly from S3. | |||
=== The Plan === | |||
* When I build the production infrastructure, I will configure an S3 bucket for each user | |||
* Max 1GB total; max 25MB file size | |||
* Common uploads: PDF receipt, PDF file, Word/Excel/PPT documents, Screenshots, Photos, Short videos | |||