Iron.io is pleased to announce named schedules as a feature in its IronWorker service. Giving names or labels to schedules may seem a small feature but it’s been a common request from a number of users managing large workloads.
|Docker in Production at Iron.io|
Earlier this year, we made a decision to run every task on IronWorker inside its own Docker container. Since then, we’ve run over 300,000,000 programs inside of their own private Docker containers on cloud infrastructure.
Now that we’ve been in production for several months, we wanted to take the opportunity to share with the community some of the challenges we faced in running a Docker-based infrastructure, how we overcame them, and why it was worth it.
|Long-Running Workers are Now Available in IronWorker|
Iron.io is happy to announce long-running workers are now available within IronWorker. Up until now, workers running on the platform have been limited to 60 minutes in duration.
Users on Production and Enterprise plans or using Dedicated Clusters can now have workers that run for hours at a time. This gives users greater flexibility to handle even more extensive asynchronous workflows. Continue reading “Iron.io Adds Longer Running Workers”
FFmpeg is the leading cross-platform solution to record, convert and stream audio and video. Dealing with audio and video can eat up resources, making the activity a great fit for IronWorker by moving the heavy lifting to the background.
In the past, usage of FFmpeg with IronWorker would require that our users include and install the dependency within each worker environment. In order to streamline that process for developers, we’ve included FFmpeg in an IronWorker stack as a custom runtime environment specifically meant for video processing. Continue reading “New FFmpeg IronWorker Stack For Easy Video Processing”
|Message Size Increases from 64KB to 256KB|
Large message sizes are now available within IronMQ. We have increased the message size from 64KB to 256KB.
This increase was originally in response to some uses cases around XML but also allows the service to handle almost every need possible when it comes to messaging. The increased sizes are available on Developer plans and above.
|IronWorker Now Offers Dedicated Worker Clusters|
Dedicated workers clusters are now available within IronWorker. Sets of workers can be provisioned to run tasks on a dedicated basis for specific customers. The benefits include guaranteed concurrency and stricter latencies on task execution.
This capability is designed for applications that have a steady stream of mission-critical work or organizations that have greater requirements around task execution and job latency.
|IronWorker Can Now Handle Larger Tasks|
We’re pleased to announce the availability of high-memory workers within IronWorker. This new capability will provide greater processing power to tackle even more ambitious tasks.
The added boost to the IronWorker environment is perfect for tasks that consume large amounts of computing resources – tasks that might include big data processing, scientific analysis, image and document processing, and audio and video encoding. Continue reading “Iron.io Releases High Memory Workers”
|Message Queuing for Public, Private, and Hybrid Clouds|
Today we’re excited to release IronMQ Enterprise, our cloud-native message queuing technology for large enterprise and carrier-grade workloads.
IronMQ Enterprise features a more advanced backend persistence layer, improved message throughput and latency, and, for the first time, deployment options for on-premise, private and hybrid cloud configurations. With IronMQ, enterprises can move the power of the cloud behind the firewall. Continue reading “Introducing IronMQ Enterprise”
Delivering Improved Performance + On-Premise and Hybrid Cloud Options
Today we announced IronMQ Enterprise, a set of offerings that includes more flexible configuration options including deployment on-premise and within private clouds as well as improved performance around message throughput and latency.
At the heart of this release is IronMQ v3, our latest version of IronMQ. A lot of work went on behind the scenes to improve the core messaging engine and so we wanted to use this post to give you some of the details on the efforts by the Iron.io team. Continue reading “IronMQ Enterprise: Powered by IronMQ v3”
Real-time logging of workers tasks is a popular feature in IronWorker. We provide an interface to third-party logging components and services which allows you to send your log output to any syslog endpoint and see the output in real-time.
Prior to this, you had to wait for your task to finish before being able to view a log file within the IronWorker system. To capture and view the data, you can run your own syslog server or you can use logging services such as Papertrail, Loggly, and Logentries. Continue reading “Real-time Logging for IronWorker with Logentries (repost)”