4 ms·
Cool. I really like the UI. Response times are slow-er than I would have originally thunk, but I'm sure that's a side effect of the HN hug. Are you saving thes
by joshmn 9y ago
Cool. I really like the UI. Response times are slow-er than I would have originally thunk, but I'm sure that's a side effect of the HN hug.
Are you saving these "bins" as files, and then serving them? Or are you putting them into a database? Mostly curious. :)
- mr_ali3n 9y agoThank you :) yea, kinda overwhelmed right now with the traffic, should sort out once the dust settles down. As far as your question goes, I don't store them as files, they are in DB. The file is fine for a temporary run, not great when it comes to scaling.
- arikfr 9y agoWhy not host them on S3? You can probably serve them directly from there too.
- hdhzy 9y agoBut the URL would not be that pretty, would it?
- adnanh 9y agoyou could set up an nginx proxy in front of it, or use the S3 static website feature with custom domain
- arikfr 9y agoWhy not? You can assign a domain to S3 buckets. It can be just as pretty as it is today. The only difference is if he serves them directly from S3, the domain will be different from the creation API. But considering the additional features he's planning on adding, he will probably need to proxy S3 anyway, so not sure if it's worth it in this case. But for something of the scope of the current API, S3 is the perfect solution.
- arikfr 9y agoWhy not? You can assign a domain to S3 buckets. It can be just as pretty as it is today. The only difference is if he serves them directly from S3, the domain will be different from the creation API. But considering the additional features he's planning on adding, he will probably need to proxy S3 anyway, so not sure if it's worth it in this case. But for something of the scope of the current API, S3 is the perfect solution.