Cloud Foundry vs Kubernetes: What are the differences?
What is Cloud Foundry? Deploy and scale applications in seconds on your choice of private or public cloud. Cloud Foundry is an open platform as a service (PaaS) that provides a choice of clouds, developer frameworks, and application services. Cloud Foundry makes it faster and easier to build, test, deploy, and scale applications.
What is Kubernetes? Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops. Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
Cloud Foundry and Kubernetes are primarily classified as "Platform as a Service" and "Container" tools respectively.
Some of the features offered by Cloud Foundry are:
- Application and services centric lifecycle API
- High performance dynamic routing
- Buildpack support
On the other hand, Kubernetes provides the following key features:
- Lightweight, simple and accessible
- Built for a multi-cloud world, public, private or hybrid
- Highly modular, designed so that all of its components are easily swappable
Cloud Foundry and Kubernetes are both open source tools. Kubernetes with 55.1K GitHub stars and 19.1K forks on GitHub appears to be more popular than Cloud Foundry with 605 GitHub stars and 532 GitHub forks.
Google, Slack, and Shopify are some of the popular companies that use Kubernetes, whereas Cloud Foundry is used by Intel, VMware, and SBT Aqua. Kubernetes has a broader approval, being mentioned in 1048 company stacks & 1099 developers stacks; compared to Cloud Foundry, which is listed in 8 company stacks and 13 developer stacks.
What is Cloud Foundry?
What is Kubernetes?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Cloud Foundry?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
It's a little bit complex to onboard, but once you grasp all the different concepts the platform is really powerful, and infrastructure stops being an issue.
Service discovery, auto-recovery, scaling and orchestration are just a few of the features you get.
Just tinkering with it for personal use at this stage based on positive experience using it at work. Plan to use it for high traffic distributed systems if not using a managed hosting service like Heroku, AWS Lambda, or Google Cloud Functions. Reasons for using instead of these alternatives would be cheaper cost at higher scale.
Good existential question. Kubernetes is painful in the extreme - especially when combined with Ansible. The layers of indirection are truly mind altering. But hey - containers are kewl!
Our developer experience system is on Kubernetes (Google Kubernetes Engine at the moment). We would like to expand our Kubernetes clusters over other Kubernetes engine.
Easy host and monitor the application on the cloud, using a platform that is hight integrated with Spring Framework, but is also agnostic of technology
Kubernetes is used for managing microclusters within our AWS infrastructure. This allows us to deploy new infrastructure in seconds.