dyno

The updated help pages only mention the scenario of a worker dyno running along a web dyno.

I run a simple web dyno with a worker dyno that sends out 20 emails/day.

On the new free dynos, you now get a free worker dyno, but the tradeoff is that the app must sleep for 6 hours/day.

What kind of savings could one expect hosting an API with this vs a heroku standard dyno?

Then the next hit will take longer while the dyno spins up before it returns.

It then deploys to heroku - creating a mongodb instance and a web dyno.

Pricing wise it compares well to a $7 dyno or $9 Postgres instance.

The costs grow if you get traffic, but through careful management (such as packing multiple processes into one dyno), you can reduce costs.

You could set up your own instance on a free heroku dyno, assuming it doesn't do anything that requires it to run 24/7.

It's unclear what happens to apps which just have a single worker dyno.

The e-mail clears it up: Hobby — Run a small app 24x7 with the Heroku developer experience for $7 per dyno per month.

I have no problems with the pricing, but dyno performance and memory has been the same for, what, 5 years?

But also quite expensive after you add on dyno, Postgre/Redis, and "addons." What about Heroku do you like/appreciate that justifies the slightly higher costs?

Airliners are not a Heroku dyno that you can "push code" into.

Off the top of my head, the only thing that wouldn't work is the "Currently Viewing" counter, which relies on this all running on a single heroku dyno.

One of the more notable ones was the switch from an "intelligent" request routing mechanism (Heroku's routing mesh would route requests to dynos based on their load) to a random load-balancing scheme (blind, with no regard for existing dyno load), causing requests to frequently be routed to overworked dynos while leaving open ones idling and twiddling their virtual thumbs.