When implemented effectively, Continuous Delivery (CD) embraces the DevOps philosophy of collaboration between traditionally separate teams: development and operations. CD is the automated implementation of the build, deploy, test, and release process. With CD, software is always in a releasable state. With every change to any part of the software system — infrastructure, application code, configuration, or data — a release candidate goes through a delivery pipeline where the software is created, environments are built, databases are constructed, tests are run, and software is deployed. Many tools make up a platform capable of moving the software system along this pipeline.


 In this paper we will talk about,   How a multi tenant  Java  enterprise web application is built using AWS  and Elastic Beanstack



1.0 IBM Continuous Delivery

2.0 Practical Devops- ISBN

3.0 D-Zone Multitenant Architecture

4.0 AWS In Action- ISBN

5.0 Practical Github- ISBN

6.0 Jenkins

7.0 Chef puppet.


How A Real-Estate Development  Company  Avoided Cost and Time Overrun with Cloud Based Alfresco Collaboration Server


A Real Estate Developer save $10 million and more by avoiding Cost Overrun and avoiding Deadline Penalty

A Real  Estate  Developer in Canada was in the process of developing  a shopping mall  complex in Canada.  The shopping mall was  a complex development and communication and coordination was  of key importance. The list of departments that was involved in the project  approval are large and diverse. The list below is a partial summary:


Go to top