Cloud Foundry to Kubernetes migration

Cut expensive licenses while accelerating cloud migration with our cloud-native container-based microservices platform.

$1M+
cost savings
1000
of services
10x
speed to market boost
Boost efficiency with a cloud-native stack

Boost efficiency with a cloud-native stack

Before cloud gained widespread adoption, companies often deployed Pivotal Cloud Foundry in on-premise data centers as a platform‑as‑a‑service solution. When migrating to the cloud, it is a good time to move to a cloud-native Kubernetes stack and adopt containers and immutable infrastructure. Cloud services such as GKE, EKS, and AKS, coupled with Grid Dynamics’ microservices and CICD platform accelerator provide a reliable foundation and can boost speed to market of migration programs. Database and caching managed services provided by most cloud providers will eliminate the need for custom deployment.

Migrate microservices to containers

Migrate microservices to containers

While Pivotal Cloud Foundry has recently started embracing containers, most enterprises rely on proprietary application packaging and deployment provided by PCF. Migration to containers and Kubernetes increases reliability by enforcing immutable infrastructure and infrastructure-as-code best practices, while keeping the infrastructure footprint small.

Increase speed to market

Increase speed to market

Kubernetes-based microservices platforms coupled with service mesh technologies provide a solid foundation for lightweight continuous delivery processes. Immutable infrastructure backed by containers helps to  minimize the number of configuration issues across environments. As a result, migration to k8s will at least maintain or further improve speed-to-market provided by PCF, and decrease the cost of environments.

Improve the development experience

Improve the development experience

While Cloud Foundry has a very static view on application development and deployment, k8s provides a robust but flexible platform. As we migrated clients to k8s, developers praised their newfound increased agility, greater sense of control, and the ability to deploy applications without having to involve support teams. This ultimately led to higher productivity, fewer defects during deployments, and a better DevOps culture.

Save millions on license costs

Save millions on license costs

A Pivotal Cloud Foundry license is expensive. While it may have been justified for data center deployments, it’s not the case for the cloud. Modern cloud providers enable building rich microservices platforms with no additional license costs. Companies can improve productivity, speed to market, and efficiency, while migrating to modern container-based or serverless technologies. This can be coupled with a variety of databases, caching, and messaging technologies available as managed cloud services.

Attract development talent

Attract development talent

Cloud Foundry is an old technology, which is being generally replaced with container-based platforms. New development is primarily done in Kubernetes or the serverless cloud-native stack. Most of the innovation is happening there and it is easier to find developers who know containers, k8s, or cloud, than experts in PCF.

Migration from Cloud Foundry to cloud-native Kubernetes microservices and CICD platform starts with an assessment of the application portfolio. This includes the existing continuous delivery process and underlying technology stack. A number of considerations, such as the connectivity between applications, security requirements, technology stack dependencies, and complexity of applications, are made to determine the right sequence of migration. The migration is then done in batches. 

As applications deployed in Cloud Foundry usually follow modern microservices and 12-factor design best practices, only limited modifications of application code are needed. After the base microservices and CICD platform is deployed in the cloud, applications are configured for packaging in containers and to use cloud-native dependencies such as DBs, caching, and messaging. Applications are then deployed and tested, data is migrated, and after final testing the production traffic is switched. The process then repeats for the next batch of services and applications.

How do we approach migration?

The primary goal of the microservices platform is to provide development and SRE teams with a solid foundation to develop, package, test, deploy, and operate applications and services designed according to microservices architecture patterns. It helps to adopt and enforce microservices architecture in an enterprise environment and realize the benefits of microservices, immutable infrastructure, and infrastructure-as-code. Modern digital environments include hundreds to thousands of microservices, and the platform automates all aspects of application deployment and lifecycle management, enabling autonomous operations.

How does the microservices platform work?

Technology stack

We focus on migrating applications from Cloud Foundry to Kuberenetes based platforms, coupled with Istio service mesh, and powered by cloud database, caching, and messaging services. In some cases, we bring existing open source technologies, such as Kafka, Redis, or MongoDB, to the cloud to simplify the migration process. We use immutable infrastructure and infrastructure-as-code best practices with Hashicorp technologies such as Terraform, Packer, and Vault.
Technology stack
Continuous Delivery Blueprint
Book
Continuous Delivery Blueprint
This book is a comprehensive guide to building a robust and efficient change management process at scale.

We bring more than 10 years of experience in migrating Fortune-1000 enterprises from on-premise environments to the cloud while moving applications from expensive PaaS products to container-based microservices platforms. We have saved our clients millions of dollars in annual license costs while improving developer productivity and achieving a 10x increase in speed to market using open source-based cloud-native technologies.

We provide flexible engagement options to plan and execute migration from Cloud Foundry to Kubernetes. Clients can take advantage of our accelerators to increase their speed to market and reduce risk. Contact us today to start with a workshop, discovery, or PoC.

Discovery

If you want to migrate from PCF to k8s, but aren’t sure where to start, we recommend a 2 to 3 week discovery phase where we can take a deeper look at your current application and analytics stack, design the optimum solution, and build out a roadmap.

Proof‑of‑concept

If you have already identified a specific use case for cloud migration, we can start off with a 4 to 8‑week proofof‑concept project to deliver tangible results for your company.

Workshop

We offer free half-day workshops with our top experts in cloud, microservices, data, and DevOps to discuss your optimum cloud migration strategy, opportunities, and industry best practices.

Demo

We offer free demos of our accelerators. As a part of a demo, we will share our point of view on the most effective and efficient migration strategies and discuss case studies from Fortune-1000 clients.