Over a million developers have joined DZone.

How Apprenda’s PaaS Onboards Existing and New Applications

DZone's Guide to

How Apprenda’s PaaS Onboards Existing and New Applications

· Cloud Zone ·
Free Resource

Learn how to migrate and modernize stateless applications and run them in a Kubernetes cluster.

Existing application architecture is essential for future development. It doesn’t go away because of cloud, fads, or new architecture patterns. Apprenda’s Enterprise PaaS supports new architecture patterns and, historically, 80% of your existing application portfolio (see the graph above). For most of the Fortune 500, this means hundreds or even thousands of applications that need to be enabled for the cloud.


Apprenda’s Client Services department has developed a five-phased approach to onboarding applications:

  1. Developer Workshops – Apprenda runs workshops to teach line-of-business developers about central IT’s new PaaS. The training usually includes 15 to 20 application managers. Typically, those managers will own at least five applications each. This process begins the application selection and developer education process.

  2. Application Scorecard – The application managers, with the help of Apprenda’s Client Services department, completes the in-depth scorecard for assessing the readiness of each app. The scoring can be done during the workshop described in Step 1, through a Microsoft Word template, or through an online questionnaire. Off-the-shelf Java applications like JTrac, JForum, Jenkins, and Apache Continuum deploy to Apprenda without modification.

  3. Application Analysis – Apprenda’s engineering experts examine the data collected for each application and stack rank the applications in order of complexity. Typically, each manager in the workshop will have at least one application that will move to the platform with nothing more than repackaging and deploying it to Apprenda: a simple “re-platforming.”

  4. Level of Effort – The applications that require no modification are on-boarded first. For a typical, broad app portfolio across lines of business, see the graph above.

  5. Onboarding – Application managers deploy applications to the PaaS. If there are difficulties, Apprenda Client Services will help analyze the app, logs, and process.

  6. Repeat – The steps above are repeated until all the desired applications are onboarded onto the PaaS.


Earlier this week, I explained how Apprenda supports existing applications. To get the hundreds or thousands of existing apps onto the platform, it is important that the vendor has a defined workflow. In this blog, I outlined that process.

Lastly, the vendor needs to have a history of implementation with customers. Apprenda is the Enterprise PaaS powering the most Fortune 500 applications. In order to do this, Apprenda has to support the majority of the applications and app architectures. Historically, Apprenda has been able to onboard hundreds of apps in months:


For more technical information on how applications move to Apprenda, please see the following documentation:

Join us in exploring application and infrastructure changes required for running scalable, observable, and portable apps on Kubernetes.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}