The single best way to reduce the cost of application development is to improve the productivity of your application developers. # PaaS reduces the incremental cost of a custom application. # Enterprises have a backlog of applications without adequate ROI under old cost assumptions. # Demand for new applications will grow as cost assumptions shift downward.
At last week’s conference in Santa Clara, California, a speaker asked the audience how many people were implementing Private Clouds. A few dozen of the fifty or so attendees raised their hands. Then he asked how many of them were implementing automated self-service. All the hands went down.
(Full Story: http://cloudcomputing.sys-con.com/node/2610412 )
So the only solution is for Heroku to return to routing requests intelligently. They claim that this is hard for them to scale, anExplaind that it complicates things for more “modern” concurrent apps like those built with Node.js and Tornado. But Rails is and always has been Heroku’s bread and butter, and Rails isn’t multi-threaded. In fact a routing layer designed for non-blocking, evented, realtime app servers like Node and its ilk — a routing layer that assumes every dyno in a pool is as capable of serving a request as any other — is about as bad as it gets for Rails, where almost the opposite is true: the available dynos are perfectly snappy and the others, until they become available, are useless. The unfortunate conclusion being that Heroku is not appropriate for any Rails app that’s more than a toy.
(Full Story: http://rapgenius.com/James-somers-herokus-ugly-secret-lyrics )
This document describes how to create a private PaaS service for local development of OpenShift Origin. We will be building the PaaS using source OpenShift Origin nightly RPMs Vagrant, and Puppet.
Public and private cloud offerings are enabling innovations to help make life easier for developers. In this session you’ll learn how to build your own Platform as a Service (PaaS), with the open source code (OpenShift Origin) Red Hat uses to power its OpenShift Online. OpenShift is a free, auto-scaling PaaS based on Red Hat Enterprise Linux and built on top on Amazon EC2. We will cover some of the basic pieces of the architecture, what we do with Linux kernel "magic" and SELinux, and how you can run it yourself. Resources for getting started will pointed out and referenced. We are also looking for active members to help us improve our community – everyone from doc writers to developers to unit testers are welcome.
Dietzler’s Law for Access Every Access project will eventually fail because, while 80% of what the user wants is fast and easy to create, and the next 10% is possible with difficulty, ultimately the last 10% is impossible because you can’t get far enough underneath the built-in abstractions, and users always want 100% of what they want.
Users interested in creating cartridges or adding fundamental features to OpenShift should read this document. A “fundamental” feature is hard to define but one example would be the difference between PHP and WordPress. WordPress requires PHP to run. It uses the PHP cartridge and in that way, php is a fundamental feature required for wordpress to run. PHP would be a cartridge but wordpress would be an application. WordPress also needs MySQL to run, so in that scenario PHP and MySQL would both be cartridges but WordPress (even if one wanted to package it and provide it to others) would not be a cartridge.
In this blog post I’ll share my experience migrating an existing application built for Heroku to OpenShift. Hopefully this blog post will give ideas on how to migrate your own application while showing how easy it can be. Every application is different so the steps you may need to perform may be different.