Another one of our most requested features is now out in the wild: long polling. Long polling reduces the number of requests you need to make on an empty queue by not returning immediately when there are no messages available. Instead, IronMQ will wait until a message becomes available or until the “wait” time has passed (maximum 30 seconds). Continue reading “IronMQ Long Polling”
|Iron.io adds CORS support|
Iron.io is pleased to announce the introduction of support for Cross-origin Resource Sharing (CORS). This capability means that developers have even easier access to the Iron.io platform from desktop and mobile browsers and other client devices.
|Custom Runtime Language Environments in IronWorker|
Iron.io announced today the introduction of custom language environments within its IronWorker processing platform.
Instead of a single standard environment, developers can now define runtime environments and write workers for specific language versions.
IronWorker already supports all common languages including PHP, Ruby, Python, .NET, Node.js, Java, Go and binary files, but this release adds in finer grained support for specific language versions including Ruby 2.1, Python 3.2, Mono 3.0, and others. (The full table can be seen below.) Continue reading “Iron.io Launches Custom Runtime Environments for IronWorker”
|Alerts can now be set on queues to trigger actions.|
Iron.io is pleased to announce the release of alerts for IronMQ. IronMQ is a cloud-based message queuing service that offers high scale and high availability. It provides pull and push queues – meaning processes can get messages (pull) and events or the queue can push messages to processes and other endpoints.
|IronMQ is now available in Europe|
Iron.io is happy to announce today the launch of IronMQ services in Europe. IronMQ EU provides the full functionality of IronMQ as is currently available in the US and is available to the public in general release.
IronMQ offers two endpoints in Europe – AWS EU-West and Rackspace-LON. These endpoints join services in AWS US-East (N.Virginia) and Rackspace-Ord (Chicago). Switching regions and clouds is as simple as changing endpoints within messaging clients and can be accomplished on the fly. Continue reading “Iron.io Launches IronMQ in Europe”
IronMQ has had push queue capabilities for a while now. Push queues allow messages/payloads to be pushed to one or more endpoints and is a very popular feature. Within IronMQ push queues, up to 100 subscribers can be added – with the routing being either unicast (pushing to 1 subscriber) or multi-cast (pushing to all subscribers).
Push queues eliminate the need to poll as well as provide access to messages/payloads more promptly. (As soon as the message comes in, it gets distributed to one or more subscribers.) Continue reading “Push Queues + Error Queues = Better Queue Processing”
IronSharp is a great new contribution from a long-time supporter and user of IronMQ, IronWorker, and IronCache.
Jeremy Bell created IronSharp to provide updated access in .NET to all Iron.io services. It’s a simple solid library that wraps the API calls for IronMQ, IronWorker, and IronCache and includes support for the latest Iron.io features. (It also has a great logo and GitHub page.) Continue reading “IronSharp — .NET Client Library for Iron.io (a contribution from a user)”
You can now add queues and workers as subscribers to your IronMQ queues so now a single message post can be pushed onto multiple queues and/or start IronWorker tasks. This is often referred to as “fan-out” and opens up a lot of interesting possibilities such as:
- Multiple consumers of a single message.
- Better decoupling by adding queues as subscribers that different consumers can consume without the producer of the messages having to know about it.
- Better performance since you only need to push one message then let IronMQ deal with distributing it to multiple queues.
One of the most common feature requests we get for IronWorker is the ability to view logs in real-time while your workers are running. Until now, you had to wait for your IronWorker tasks to finish before being able to view the log and it can be pretty frustrating to try to debug your workers if you have to wait for a task to complete to see the log — especially if it’s a task that takes a long time to finish.
Now you can send your log output to any syslog endpoint so you can see it in real-time. You can run your own syslog server with something like syslogd or Splunk, or you can use a “logging as a service” provider such as Papertrail or Loggly. I’ll show you how to use Papertrail in this post. Continue reading “Real-time Logging for IronWorker”
We’re happy to announce that IronMQ is now available in the Rackspace Chicago (ORD) region. A year and a half ago, we launched IronMQ on Rackspace in their Dallas / Fort Worth (DFW) region and today we’re expanding our footprint into another Rackspace data center.
Our mission for IronMQ is to be the message queue for the cloud, meaning we want to make it the best MQ around and make it available everywhere. Adding the Rackspace ORD region brings us one step closer to accomplishing that mission. Continue reading “IronMQ Now Available on Rackspace ORD (Chicago)”