Cloud Services: An Academic Perspective

An academic entity – more concretely, a research laboratory – resembles a stateful function: It receives input and generates output based on both the input and on previously generated knowledge and results. The input is typically a mix of fancy ideas, industry necessities, as well as funding and equipment. The output encompasses publications, software and other re-usable artefacts.

In the Service Prototyping Lab, we rely on access to well-maintained cloud environments as one form of input to come up with and test relevant concepts and methods on how to bring applications and services online on top of programmable platforms and infrastructure (i.e., PaaS and IaaS). This Samichlaus post reports on our findings after having used several such environments in parallel over several months.

Continue reading


[OpenShift]( is one of the Open Source Platform as a Service cloud computing frameworks that the ICCLabs works with. For developers, deploying their application to this runtime is a simple as using the all-familiar `git` command. Currently, OpenShift supports the following development runtimes:

* node.js
* Ruby (Rack, RoR)
* Python (WSGI, Django)
* Perl (PSGI)
* PHP (CodeIgniter, CakePHP)
* Java (Java EE 6)


“[Cloud Foundry]( is an open platform as a service, providing a choice of clouds, developer frameworks and application services. Initiated by VMware, with broad industry support, Cloud Foundry makes it faster and easier to build, test, deploy and scale applications. It is an open source project and is available through a variety of private cloud distributions and public cloud instances, including” [CloudFoundry FAQ](