[olefoo]

I'm not Heroku's biggest fan, and haven't used it for more than a couple of one-off fiddles to play with the platform.

But, my sympathy is going to them, because what I see coming from Rap Genius looks like classic blame-game. So a vendors documentation was unclear and your server sucked publicly for some time? Shameful. You didn't know about it because you expected your vendors to give you extra hand-holding? That's really rough. Instead of fixing the issues and moving on, you make it the one thing that everyone thinks about when your company is mentioned... that might not be in your best long term interests.

After this, I would be hesitant to enter into any sort of relations with Rap Genius, and I'm not that sure of what they do or what their product is.

[gregd]

I'm having a hard time understanding your justification for your sympathy going to Heroku.

RG is paying for PaaS from Heroku based on documentation, sales pitches, etc. They're also paying good money for the tools necessary to make business decisions based on data collected from that PaaS. Just given the realm of customer service, why wouldn't you expect "hand-holding" from your vendor? Why is it unreasonable to have that expectation? Why is it acceptable for your vendor to have a fall down response in "optimize your web-stack"? How do you expect them to "fix" this problem without the vendors involvement? What did you expect them to do, change platforms? How are they supposed to "move on" when the issue hasn't been resolved?

Have we gotten so far away from customer service with the likes of Google, that we don't even know what that means anymore? Are we to settle for mediocrity from any PaaS because our expectations are just too high?

[olefoo]

To take an analogy from another field that, this is like a cinematographer getting bent out of shape and angry at the camera leasing company because he used a film stock his camera wasn't correctly calibrated for. From what I've read about it, it sounds like the setup on the servers had some issues that made the queue time issue into a problem where it wouldn't necessarily be for another, or even most other, customers. If you are or want to be, known as a technical company, that means you have to take responsibility for your mistakes, even if your mistake was thinking that the vendor was going to catch and fix all the mistakes and bugs in the service that they are providing to you. Building web services that are performant, stable and economical is hard work; you can't take your eye off the ball, and you can't just blindly hope that vendors will take care of your shit for you, you have to know what you're buying, and what you should be getting.

And, if you're going to go public with your complaints, it's best to do so in an understated, fact based manner. In this case, Rap Genius comes off like a guy screaming at the waiter in a fancy restaurant. They may be displeased, they may even be right about the choucroutes en sel being salted cabbage; but lot's of people around think they're making an ass of themselves.