Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3 turns out to be too expensive #11

Open
lourot opened this issue Sep 25, 2018 · 1 comment
Open

S3 turns out to be too expensive #11

lourot opened this issue Sep 25, 2018 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@lourot
Copy link
Member

lourot commented Sep 25, 2018

We use S3 to expose our DB over HTTP. Our DB is made of many json files, and for 3k users we will have about 260k files, which we refresh daily.

1000 PUTs to S3 cost $0.005. Thus this upload will cost us $40/month. On top of that come the price of storing and the price incurred by users fetching the data, but these are low.

We could for example replace these $40 by only $5 by running a t2.nano exposing the files over HTTP.

@lourot lourot added the enhancement New feature or request label Sep 25, 2018
@lourot lourot added this to the scaling issues milestone Sep 25, 2018
@lourot lourot self-assigned this Sep 25, 2018
@brillout
Copy link

Worst case in the long run is to set up database which would likely be much cheaper

@lourot lourot removed this from the scaling issues milestone Oct 28, 2018
@lourot lourot removed the assigned label Oct 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants