Site icon akquinet AG – Blog

Proof-of-Concept (POC) – Platform-as-a-Service (PaaS) Environment for social media sites


The customer (a big retail store chain) uses micro sites to implement small, time-limited areas in their web site. This proof of concept demonstrates, how the desired life cycle of a micro web site for social media activities could be realized with Openshift 2.x. The life cycle includes development, test, publish and archive. Another important aspect of this proof of concept is the scalability of the solution.

The concept contains the following aspects:

In addition, the proof of concept should specify the production environment requirements more precisely.

First Concept

OpenShift is a cloud computing platform as a service product from Red Hat (see It allows to set up a private cloud for your own applications.

The Environment here consists of two OpenShift installation: The left one for development / QA and the right one for production.


Continuous Delivery Process

The continous delivery consists of two steps: from development to test/QA and from test/QA to production.

  1. Automatic application deployment from development to QA
    • External jenkins job clones the git repository and sets a tag on the external scm manager
    • External jenkins job creates a new application in the test environment with the tagged version
  2. Automatic application deployment from test/QA to production
    • External jenkins job creates a new application in the production environment with the tagged version. The application is highly available (high-availability proxy).

The system is rolled back to the previously tagged version in case of an error.

Scaling and Availability

Scaling and availability is achived in two levels. The first level use the internal OpenShift high-availability proxy with a minimum of two and a maximum of four gears. The second level is an external load balancer for two high-availability proxy instances.


The implementation is based on OpenShift 2.1 with one broker and three nodes. Multiple nodes are necessary to proof scaling and availability. A front end apache is used for specific customer configuration (self defined error pages, ….).

Life Cycle Concept

Initialisation Phase

Development Phase

Production Phase

End of Life


The concept shows that a simple and independent development can be combined with continuous delivery and high avaliabilty achieved through OpenShift.

Exit mobile version