goPaddle Beta 2 – Release Notes

We have added some cool features in our Beta 2 release. We have categorised them as General, Continuous DevOps and Portability.


  1.  Application Representation:
    Gives a graphical representation of the applications and the related services, thus hiding the complexity of infrastructure management from the developers.
  2. Demo Cloud Accounts, Applications & VirtualMachines:
    A  registered user can now user our demo VMs i.e., named as Source and Target VMs to explore goPaddle’s rich and finest features. Source VM has a default application running and you can port this running application and deploy the application as containers on to the Target VM.

Continuous DevOps:

  1. Deployment as Kubernetes Services:
    goPaddle deploys the applications as Kubernetes services on Google Container Engine (GKE) along with replication controllers. This enables auto-healing of services and deploying multiple applications sharing the same port.
  2. Better Graphical Representation of the services:
    The enhanced graphical representation is easy to understand the service dependencies. Application view got enhanced in such a way that, each service will have an icon and the port details on which it is connected to other services.
  3. CI/CD Jenkins Plugin:
    Jenkins plugin for continuous integration and deployments. This plugin helps you to automatically deploy the applications across cloud platforms such as Kubernetes. Plugin retrieves the application details from goPaddle portal and deploys it on the Kubernetes platform which is already configured and managed by goPaddle.

Porting applications across platforms:

  1. Application Re-Configuration:
    goPaddle’s reverse engineering process discovers the application stacks along with the application specific configuration file(s). In this release goPaddle allows you to customize or delete the application specific configuration files before dockerizing the application. Upon successful customization of configuration, you can proceed to dockerizing the application and launch the application with the latest configuration on to a VM. For example, a springboot application which has database as mysql, before containerizing this application you want to change the data in the database with the one that you have backed up earlier. In this scenario, goPaddle allows you to configure the path of backed up database data. Once you containerize and launch this blueprint you will see that springboot application deployed with earlier data in database.
  2. Detection of external services:
    If the service depends on external services which cannot be ported, then they are detected and reported at the time of porting the applications.
  3. Distributed Application discovery:
    goPaddle is capable of generating a single blueprint even when the application components are distributed or spread across different machines. Once the distributed application is dockerized/blueprinted, the whole application can be launched on to a single VM as containers i.e., each component of the application will be launched as individual containers. This results in huge cost savings. For example, you have an application with apache, tomcat and mysql as components. Apache and tomcat servers are running on a VM and MySql database is running on another VM. When goPaddle discovers the VM on which Apache and tomcat are running, it also discovers the MySql running VM instance and shows this linked VMs in a graphical representation too. Once you dockerize this distributed application, all these components/ services are stitched together into a single blueprint.
  4. Native Application Deployments:
    Applications and services can now be ported and deployed as native or container based applications on the target IaaS, PaaS or CaaS(Container Clusters) platforms.
  5. Support for other platforms:
    We have added support NodeJS, golang, Redis server porting.Further Information Visit below Link

Be the first to comment

Leave a Reply

Your email address will not be published.