537 karma · joined November 14, 2011
Saying this, there's lots of things deployable to Heroku right now, and even more via the Buildpacks system. Yes, at first Heroku was just Ruby, but those days are long gone, most modern platforms that run on UNIX are deployable to Heroku in just a few minutes.
As for current invoices amount, the old dashboard used to show you your current usage. I'm not sure when this got lost, but the new dashboard doesn't have it.
I can pretty much guarantee that Heroku are fully aware of both of these problems and acting on them…
I'm generally only seeing a lag of a few seconds at most, and no lost requests. I would look at your code and see what improvements you may be able to make.
This new attempt doesn't seem to fix my biggest gripe with the whole system (and in the grand scale of things, that's a pretty small gripe)
Heroku places no requirements on your code that you wouldn't find through general best practise when building scalable applications. A lot of people will cite the read-only filesystem as a special requirement (which requires S3 or similar), but this is a common requirement with clustered systems. Yes you might have a local SAN that you can use as a local filesystem but the point is the same.
With the multiple applications I've deployed to Heroku I don't think any would not run on a 'regular' VPS as is. There's no Heroku specific code in there period. In fact, if I have changed my approach to better suit hosting on Heroku, it's generally been changing it to a better approach that would suit all types of hosting.