Delivering on the Promise of Multicloud Lambda-like Functionality

multicloud-takeoff

In February, we launch a beta called Project Kratos. It promised to bring Lambda-like functionality to any cloud – public, private, hybrid or on-premises. As we quickly approach Q4, February seems like a long time ago, but so much has happened since then.

Over the past seven months, serverless computing has gained momentum as more than just the hot topic of the moment. Because it allows enterprises to build and deploy applications and services at scale on flexible platforms that abstract away physical infrastructure, it’s quickly becoming a must have for the modern enterprise. It will soon be a competitive advantage for those already implementing it.

Our journey with serverless has also moved from a project announcement full of promises to the solution that is widely available today.  First, in April, we announced the general availability of its multicloud solution. Since then, we’ve systematically partnered with leading cloud providers to support multicloud development.

In April, Iron.io announced its partnership with Mirantis to bring event-driven, serverless functionality to the OpenStack community. The joint solution enables enterprise developers using OpenStack to deliver applications and services faster through the serverless experience provided by Iron.io.

In May, Iron.io announced its collaboration with Cloud Foundry Foundation, home of the industry-standard multi-cloud platform, to integrate the Iron.io API with the Cloud Foundry platform.

In June, Iron.io brought the serverless experience to Red Hat OpenShift — a pairing that provided users with an end-to-end environment for building and deploying applications at scale, without the headaches of complex operations.

And in August, Iron.io announced its strategic partnership with Mesosphere, enabling microservices and serverless computing for modern data centers. Joint customers using Mesosphere’s Data Center Operating System (DC/OS) with Iron.io could experience enhanced flexibility to develop their hybrid cloud strategy and run distributed job processing across heterogeneous environments.

Yesterday, we added an announcement that serverless functionality is now available on Cloud Foundry and Iron.io supports Diego as a runtime for Iron.io workloads. Iron.io is now able to be deployed on top of Cloud Foundry, run inside of Cloud Foundry, and scale out Cloud Foundry containers.

Wow. I was here for all of it and it still seems like a lot, but it’s only the beginning. The Iron.io team is committed to bringing a serverless experiences to developers and companies far and wide.

If you want information on how we define serverless and why the world is moving this way, check out Chad Arimura’s presentation Best Practices for Implementing Serverless Architecture from the O’Reilly Software Architect conference or Dave Nugent and Ivan Dywer’s great Fireside Chat about serverless computing.

Introducing Lambda support on Iron.io

AWSonDocker_revised

Serverless computing has become a compelling model for companies to add business value without their development teams having to worry about provisioning, managing and scaling infrastructure. The concept is that developers write code that performs business logic based on  some specific input data, and the platform handles the details of:

  • Where to run it: Use some machine with available capacity in its pool
  • When to run it: Either event-driven or scheduled
  • How to run it: Decouple your developers from your runtime. You do not have to be concerned about whether your program is running on bare metal, in a VM or in some sort of container

(more…)

Message Queues & Workers: the Heart of Modern Infrastructure

Message Queues + Workers

Thanks to Sonny Abesamis for the base image! CC BY 2.0

Increasingly, message queues and workers are intertwined with the language of modern infrastructure. You might rely on explicit solutions like IronMQ or IronWorker. You might not. Whether you do or don’t is irrelevant: MQs and workers are in everything these days.

MQs and workers are hidden heroes, quietly powering a lot of the technology that many of us rely on. They’re core components in programming languages, MVC frameworks, and even web servers.

As a result, when making infrastructure decisions a good understanding of both MQs and workers is essential. The white paper below will take you from a fuzzy understanding to a well-versed conceptualization for both MQs and workers.

Download the latest white paper from Iron.io: a Refresher on Message Queues & Workers.
Give it a read and let us know what you think!

$8 Million Series A Will Enable Iron.io To Take Its Mission to a New Level

ironio-team FY15

When Travis and I founded Iron.io, we set out to create a beautiful developer experience for scaling your apps job processing system. If you’ve written apps that had to scale, managing the sometimes millions of events and tasks using queues and workers is extremely painful, error prone, and let’s face it, non-strategic. This type of plumbing is pretty unsexy to most developers, but to us, it meant developer empowerment. Plumbing that empowered a single developer at Untappd to build and scale to millions of beer check-ins per night, and a developer at Bleacher Report to deliver millions of push notifications in minutes without ever worrying about infrastructure. As we watched these use cases grow, we knew we were on to something.

Today, thousands of organizations rely on Iron.io for their event-driven applications. From small mobile gaming companies to the world’s largest global enterprises, we are serving billions of events per day through the Iron.io platform across a variety of cloud infrastructure providers as well as private data centers. This hybrid architecture gives our enterprise customers choice and control, while still delivering on our original promise to empower developers to build amazing things.

On the heels of this success in the market, I’m thrilled to announce that we’re accelerating that mission with $8 million in Series A financing, led by our long-time investor, supporter, advisor, Steve Anderson, founder of Baseline Ventures. We’re thrilled to have the continued support of our early investors Bain Capital Ventures, Divergent Ventures, Cloud Capital Partners, and Ignition Partners.

Everyday, I’m humbled by the amazing stories we hear from our customers and honored to work alongside a brilliant team of 40 and counting. This funding will fuel our growth and enable us to deliver on core enterprise features, further extending our lead as the most powerful, scalable, and developer friendly event-driven platform available.

Chad Arimura, CEO and Co-Founder

Project Thor Will Deliver First True Hybrid IronWorker Solution

Today, Iron.io announced Project Thor, which is developing the world’s first hybrid job processing system. This is unlike anything we’ve done to date. Unlike previous IronWorker technology, Project Thor is architected to deliver the power of Iron.io to any server in the world in minutes.

With Project Thor, the Iron.io IronWorker Docker container is deployed on a company’s own servers, which then communicates with the Iron.io API. This brings the power of Iron.io’s event-driven computing service to the Enterprise in just a few easy steps. Project Thor seamlessly integrates with existing solutions for container deployment, such as OpenShift by Red Hat, Cloud Foundry, OpenStack and Kubernetes.

(more…)

Iron.io Adds Derek Collison as an Advisor – Former SVP/Chief Architect at Tibco, Architect of Cloud Foundry

We’re happy to announce that we recently added Derek Collison to the Iron.io advisory board. Derek is Founder/CEO of Apcera and an industry veteran and pioneer in large-scale distributed systems and enterprise computing.  He has held executive positions at Google, VMware, and TIBCO Software and so is a great resource for technical and business insight.

Derek Collison
Iron.io Advisor

Since starting Apcera, Derek has been dedicated to delivering composable technology for modern enterprises to innovate faster. He was previously CTO at VMware where he designed and architected the industry’s first open PaaS, Cloud Foundry. Prior to that, he was one of two Technical Directors at Google where he co-founded the AJAX APIs group. He also spent over 10 years at TIBCO Software, where he designed and implemented a wide range of messaging products, including Rendezvous and EMS. As TIBCO’s SVP and Chief Architect, Derek led technical and strategic product direction and delivery. (more…)

SimpleWorker is a Citrix Accelerator Finalist!

We’re proud to announce that SimpleWorker is a finalist in the Citrix Global Challenge 2011.  Hundreds of companies were vetted and distilled down to 12 finalists based on a number of criterion, a couple of which I will highlight.
(more…)