Want an easy, scalable, highly available, zero maintenance Delayed Job backend? Look no further. Here’s a Delayed Job (DJ) backend gem that uses IronMQ. You can set it up in minutes and never have to worry about it again:
|Too many lemmings and you’ve got a problem.|
Being able to limit how many worker tasks can run at once has been one of the most requested features of IronWorker and it is available now! There are many reasons this feature is so important, here are a few of the more common use cases for it:
- Limit load on your database. If you know your database can handle X tasks at a time, set max_concurrency to X and then queue up as many tasks as you want.
- Limit requests on third party API’s to stay under rate limits such as the Facebook API and Twitter API. The Twitter API for instance, has a 150 requests per hour limit.
We’re pleased to announce IronMQ is now a preferred add-on on the Engine Yard platform.
IronMQ joins IronWorker on Engine Yard to let developers do even bigger things with their applications by providing industrial-strength ways to scale out processing and pass messages between independent processes.
Continue reading “IronMQ + EngineYard”
IronWorker now supports .NET so you can run .NET code at scale. Let your .NET workers process big data, send massive notifications, collect data from API’s, schedule tasks, etc. All in the cloud, no servers required.
Here’s a quick Hello Worker example so you can see how easy it is to get started.
Continue reading “.NET Just Got Some Iron Behind It”
|The New HUD|
The latest update to the Iron.io user interface, otherwise known as HUD, is live. Taking into account all the great user feedback we’ve received, we strived to make this release easier to use and nicer on the eyes. Here are some of the major changes:
Continue reading “The Iron.io Console (HUD) Version 4 Released – Better all around”
We have created a shiny new command line interface (CLI) and a brand new way to define your workers to make uploading your worker code a lot easier and quicker. This should fit much better into the typical developer workflow so you can push to your git repo and upload your workers from the command line. This article will walk you through making a worker, uploading it to IronWorker and then queuing up a bunch of tasks for it.
Continue reading “The New IronWorker Command Line Interface and .worker Files”
Iron.io is pleased to announce a soft-launch/beta release of IronCache, a hosted key/value data cache. It’s an elastic cloud-based solution built for storing short-term processing results and passing items between asynchronous processes. IronCache is useful for many situations where a database alone isn’t an optimal solution. The service is accessible via a simple HTTP interface and is memcached compatible. It uses OAuth to provide a simple and secure authentication mechanism.
Continue reading “Iron.io Releases IronCache (Beta)”
A hyperpolyglot is one who can speak six or more languages fluently. The term was coined by the linguist Richard Hudson in 2003 and derives from the word “polyglot”, meaning one who can speak multiple languages.
Today marks a major step forward for IronWorker as we’ve opened the platform to a wide array of new languages, vastly expanding the possibilities of what you can do with it. IronWorker aims to be a language-agnostic platform that lets developers use the language they are comfortable with and, with today’s release, we’ve come a lot closer to achieving that goal.
Continue reading “IronWorker Goes Hyperpolyglot – Adds Java, Node and Go Support”