Hacker News new | past | comments | ask | show | jobs | submit login

Indeed, serving is the easy part, once it's set up. Going offline when the DC goes offline can be completely acceptable.

It's the picture intake pipeline that eats most of the resources. If you only want to serve the same collection, or a collection you personally increase by 1-2 cats a day, then it's fine.




> It's the picture intake pipeline that eats most of the resources.

How so? Let's say you want to be somewhat competitive with imgur and handle a million images per day, and also that the peak rate is 4x your average. That comes out to 50 images per second. A thumbnail or few shouldn't really take more than a CPU-second, so you can handle that with 2-6 cheap servers. Let alone using spare cores on storage-optimized servers. And it's next to zero database load.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: