Our API is getting hammered… again. Part of this is due to a new site that’s using our API: yes.com. They’re an interesting site where people can listen to internet radio stations while live-chatting at the same time (presumably conversation revolves at least partially around the music).
I tried some temporary fixes, but I don’t know who I’m kidding: we need to have a read-only database replica for the API to be able to survive. I should have thought of it earlier, but this week really started pressing it.
I wanted to do this all in the late hours of the night, but we can’t wait any more, the site is getting rocked…
I’ll post when it’s fixed.