What is a Platform as a Service (or: PaaS) really?

I get the question from the title a lot since I started working at anynines. Which is fair enough, with the Everything as a Service trend, one easily gets the terminology confused. The extension as a service is used in many core components of cloud computing including communication, infrastructure, data and platforms (there we are!). Let’s look at a few of those in more detail.

Infrastructure as a Service

Providers of Infrastructure as a Service (IaaS) offer computers – physical or more often virtual machines – and other resources. A hypervisor – powered by OpenStack in our case – runs the virtual machines (VMs). IaaS clouds often offer additional resources such as a virtual-machine disk image library, raw (block) and file-based storage, firewalls, load balancers, IP addresses, virtual local area networks (VLANs), and software bundles on-demand from their large pools installed in data centers.

Quite possibly funniest IaaS reference in a Twitter bio ever.

Why would you use IaaS rather than ‘bare metal’? Well, cloud providers typically bill IaaS services on a utility basis (where the cost reflects the amount of actual resources allocated and consumed), which is oftentimes cheaper. (more…)

How-to use RabbitMQ in your Ruby applications

Say an application with a web front-end needs to send messages. We don’t want to send all messages synchronously because, you know, we care about website speed and response times. That’s why we’ll need a messaging broker. RabbitMQ is such a messaging broker, or: an intermediary for messaging. It gives your applications a common platform to send and receive messages, and your messages a safe place until a delivery daemon takes them from the msg bus and sends them to the corresponding receiver.

The anynines PaaS provides service credentials to your running applications via environment variables. We created the a9s_rabbitmq gem to simplify RabbitMQ configuration within your Ruby application. It supports generating credentials for the amqp and the bunny gem out of the box.


Hello, OpenStack Icehouse.

We are excited about the final release of OpenStack Icehouse. Since the Icehouse Design Summit in Hong-Kong the team of contributors added a new integrated component (Trove), completed more than 350 feature blueprints and fixed almost 3000 reported bugs. So, what’s new (read: updated) in OpenStack 2014.1?

Find source code and a complete lists of features and bug fixes, for each integrated project:
Nova (cloud computing fabric controller), Swift (Object Storage), Glance (Image Service), Neutron (Networking), Cinder (Block Storage), Keystone (Identity), Horizon (Dashboard), Ceilometer (Telemetry), Heat (Orchestration) and Trove (Database Service).

The OpenStack Icehouse Release Notes contain an overview of the key features, as well as upgrade notes and current lists of known issues.