Message Queues, Background Processing and the End of the Monolithic App (reposted from Heroku blog)

Here’s a post of ours on message queuing and background processing that we published on the Heroku blog the other day. Definitely worth checking out if you believe like us that distributed multi-tier architectures are the future of production-scale cloud applications.


Iron.io Guest Post on Heroku

Message Queues, Background Processing and the End of the Monolithic App

Platform as a Service has transformed the use of cloud infrastructure and drastically increased cloud adoption for common types of applications, but apps are becoming more complex. There are more interfaces, greater expectations on response times, increasing connections to other systems, and lots more processing around each event. The next shift in cloud development will be less about building monolithic apps and more about creating highly scalable and adaptive systems.

Continue reading “Message Queues, Background Processing and the End of the Monolithic App (reposted from Heroku blog)”

Why IronWorker is Better than Heroku Workers / Delayed Job

First off, I would like to say that we use and love Heroku, the system they’ve built is game changing and 100% awesome, but their worker system is limited and does not meet our needs. Here’s the top 4 reasons why IronWorker is better than Heroku’s worker system and Delayed Job (Heroku’s system is based on Delayed Job).

Continue reading “Why IronWorker is Better than Heroku Workers / Delayed Job”