4 ms·
Heroku and SOA
- michaelmior 12y agoThe article misses one important point about free dynos. After a period of inactivity, your dyno will be come idle. This simply means that the next request will have significantly higher latency as the dyno restarts. This latency becomes even worse if you're waiting for 10 different services to start. Of course, this isn't a problem if your app gets a reasonable amount of traffic but at that point there's a good chance you're paying for multiple dynos anyway.
- rdegges 12y agoAuthor here -- this is correct. I think it's a pretty good tradeoff though! At OpenCNAM we handled billions of API requests, and some of our internal services actually ran on a single dyno (async stuff, mainly) -- but still, it was pretty awesome.
- michaelmior 12y agoDefinitely if you have sync stuff running on the free tier, you can mostly stop caring about idling :)
- jack9 12y agoHeroku spam at nearly the same time as a massive upgrade that breaks backward compatibility, causing serious outages (or massive headaches) for a number of customers....coincidence? I think not. Heroku has proven itself to be unreliable time and time again. I have not met a capable engineer who endorses or would suggest heroku as an acceptable production platform (much less for development since the platform lacks so much control).