> Sorry to ask, would that be open sourced? No. I would have if I owned the code personally, but it wasn't in the companies interests to open source it. > Tha

> Sorry to ask, would that be open sourced? No. I would have if I owned the code personally, but it wasn't in the companies interests to open source it. > That is a little hard to warp my head around... I was there between was 2012—2013. The hardware wasn't bad, I don't remember the exact specs but it was colocated at a place in downtown TO on some decent but not crazy gear. It wasn't perfect, but it worked pretty well. For the actual image processing we just shelled out to imagemagick and I vaguely recall some fancy batch write code for keeping things like photo view counts from completely destroying the DB. We had a hardware load balancer that worked pretty good and we compiled ruby ourselves for a performance boost, though that ended up killing us this one time when there was a bug that only showed up in the compiled version of Ruby when all the dev boxes ran the universal binary. People care so much about performance, and in some cases like computer games it's totally warranted, but if at the end of the day you have a DB the DB is going to be the problem long, long, long before the application code.