{"id":414312,"date":"2022-03-10T14:00:09","date_gmt":"2022-03-10T11:00:09","guid":{"rendered":"https:\/\/en.buradabiliyorum.com\/which-cloud-platform-should-you-choose-cloudsavvy-it\/"},"modified":"2022-03-10T14:00:09","modified_gmt":"2022-03-10T11:00:09","slug":"which-cloud-platform-should-you-choose-cloudsavvy-it","status":"publish","type":"post","link":"https:\/\/buradabiliyorum.com\/en\/which-cloud-platform-should-you-choose-cloudsavvy-it\/","title":{"rendered":"#Which Cloud Platform Should You Choose? \u2013 CloudSavvy IT"},"content":{"rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_85 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-6a36b535a80f5\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #dd3333;color:#dd3333\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #dd3333;color:#dd3333\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-6a36b535a80f5\" checked aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-1'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/buradabiliyorum.com\/en\/which-cloud-platform-should-you-choose-cloudsavvy-it\/#%E2%80%9CWhich_Cloud_Platform_Should_You_Choose_%E2%80%93_CloudSavvy_IT%E2%80%9D\" >&#8220;Which Cloud Platform Should You Choose? \u2013 CloudSavvy IT&#8221;<\/a><ul class='ez-toc-list-level-2' ><li class='ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/buradabiliyorum.com\/en\/which-cloud-platform-should-you-choose-cloudsavvy-it\/#Defining_the_Platforms\" >Defining the Platforms<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/buradabiliyorum.com\/en\/which-cloud-platform-should-you-choose-cloudsavvy-it\/#Advantages_of_CloudFoundry\" >Advantages of CloudFoundry<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/buradabiliyorum.com\/en\/which-cloud-platform-should-you-choose-cloudsavvy-it\/#Advantages_of_Kubernetes\" >Advantages of Kubernetes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/buradabiliyorum.com\/en\/which-cloud-platform-should-you-choose-cloudsavvy-it\/#Deployment_Models\" >Deployment Models<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/buradabiliyorum.com\/en\/which-cloud-platform-should-you-choose-cloudsavvy-it\/#CloudFoundry\" >CloudFoundry<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/buradabiliyorum.com\/en\/which-cloud-platform-should-you-choose-cloudsavvy-it\/#Kubernetes\" >Kubernetes<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/buradabiliyorum.com\/en\/which-cloud-platform-should-you-choose-cloudsavvy-it\/#Using_Both_Platforms\" >Using Both Platforms<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/buradabiliyorum.com\/en\/which-cloud-platform-should-you-choose-cloudsavvy-it\/#Conclusion\" >Conclusion<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h1><span class=\"ez-toc-section\" id=\"%E2%80%9CWhich_Cloud_Platform_Should_You_Choose_%E2%80%93_CloudSavvy_IT%E2%80%9D\"><\/span>&#8220;Which Cloud Platform Should You Choose? \u2013 CloudSavvy IT&#8221;<span class=\"ez-toc-section-end\"><\/span><\/h1>\n<div id=\"article-content-area\">\n<img loading=\"lazy\" decoding=\"async\" class=\"type:primaryImage aligncenter size-full wp-image-15640\" data-pagespeed-lazy-srcset=\"https:\/\/www.cloudsavvyit.com\/p\/uploads\/2022\/02\/8b2ff6c7.jpg?width=398&amp;trim=1,1&amp;bg-color=000&amp;pad=1,1 400w, https:\/\/www.cloudsavvyit.com\/p\/uploads\/2022\/02\/8b2ff6c7.jpg?width=1198&amp;trim=1,1&amp;bg-color=000&amp;pad=1,1 1200w\" sizes=\"auto, 400w, 1200w\" data-pagespeed-lazy-src=\"https:\/\/www.cloudsavvyit.com\/p\/uploads\/2022\/02\/8b2ff6c7.jpg?width=1198&amp;trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"Graphic showing the CloudFoundry and Kubernetes logos\" width=\"1202\" height=\"677\" src=\"\/pagespeed_static\/1.JiBnMqyl6S.gif\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><\/p>\n<p><a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/www.cloudfoundry.org\">CloudFoundry<\/a> and <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/kubernetes.io\">Kubernetes<\/a> are two open-source technologies used to run <a href=\"https:\/\/buradabiliyorum.com\/en\/category\/download-scripts-themes-apps\/\" data-internallinksmanager029f6b8e52c=\"9\" title=\"Download Scripts &amp; Themes &amp; Apps\" target=\"_blank\" rel=\"noopener\">app<\/a>lications in the cloud. Selecting the right platform for your deployments is an important choice to maximize performance, maintainability, and the productivity of your developers.<\/p>\n<p>In this article we\u2019ll compare the characteristics of both CloudFoundry and Kubernetes. Whether you\u2019re already using one of the pair, you\u2019re trying to make the choice for your next project, or you\u2019re just curious to learn how they differ, we\u2019ll explore their capabilities and explain their use cases.<\/p>\n<h2 id=\"defining-the-platforms\"><span class=\"ez-toc-section\" id=\"Defining_the_Platforms\"><\/span>Defining the Platforms<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>CloudFoundry is billed as a <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/www.cloudfoundry.org\">development platform for cloud-native applications<\/a>. Kubernetes provides <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/kubernetes.io\">production-grade container orchestration<\/a>. Both are used to deploy applications into cloud environments but they each approach this aim from a different direction.<\/p>\n<p>CloudFoundry is a full <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/kubernetes.io\">Platform-as-a-Service<\/a> (PaaS). It provides a fully automated development experience that\u2019s founded on the <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/buildpacks.io\">buildpack<\/a> model. When you use CloudFoundry\u2019s CLI to <code>cf push<\/code> (deploy) your app, the service detects the programming languages, frameworks, and supporting technologies you use. It automatically provisions the correct cloud infrastructure to serve your project.<\/p>\n<p>Kubernetes is not regarded as a fully-fledged PaaS. It\u2019s focused on container orchestration, the practice of scaling and distributing container instances across multiple physical nodes. Deploying to Kubernetes is a more hands-on approach where you define the infrastructure your containers need.<\/p>\n<p>CloudFoundry is aware of your application\u2019s internals: it extracts meaningful information about your project\u2019s workings, then uses that to automatically assemble infrastructure components with minimal mandatory guidance. By contrast Kubernetes is a generic framework for deploying <em>containers<\/em>. It lacks any inherent awareness of your application\u2019s requirements; the shift in vocabulary from \u201capplications\u201d to \u201ccontainers\u201d illustrates how Kubernetes works with smaller units that you combine to create complete systems.<\/p>\n<h2 id=\"advantages-of-cloudfoundry\"><span class=\"ez-toc-section\" id=\"Advantages_of_CloudFoundry\"><\/span>Advantages of CloudFoundry<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>CloudFoundry gives you an application deployment platform that runs on any major cloud. Kubernetes offers a similar platform-like model but it\u2019s focused on containerized workloads. CloudFoundry adds value by giving you built-in functionality at the application-level, reducing the work you need to do when wiring components together.<\/p>\n<p>Capabilities like traffic routing, load balancing, and DNS are integrated into your deployments and configured via the CloudFoundry CLI or a simple config file in your repository. With Kubernetes you need to manually add components such as Services and Ingresses to route traffic to your containers, effectively assembling a network stack from scratch.<\/p>\n<p>A CloudFoundry installation provides a marketplace of services that are ready to add to your application. These range from databases and message queues to API gateways and integrations with third-party platforms. This makes it quick and easy to extend your stack with external components. Kubernetes doesn\u2019t have anything comparable; each component needs to be packaged as a container and manually added to your cluster.<\/p>\n<p>CloudFoundry includes other convenience features for authentication and user management. Kubernetes doesn\u2019t compare in this area either: apps need to implement their own authentication mechanisms and you\u2019re responsible for securing your cluster using tokens and <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/kubernetes.io\/docs\/reference\/access-authn-authz\/rbac\">RBAC rules<\/a>.<\/p>\n<h2 id=\"advantages-of-kubernetes\"><span class=\"ez-toc-section\" id=\"Advantages_of_Kubernetes\"><\/span>Advantages of Kubernetes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Where Kubernetes excels is when it comes to adaptable scaling and replication. Pods of containers are easily distributed across physical nodes without impacting network connectivity or relationships to other services. CloudFoundry has scaling too but the emphasis on <em>application<\/em> management means it\u2019s less granular and not so ideal for rapid load-driven auto-scaling of specific components (although this is possible with the <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/www.cloudfoundry.org\/blog\/cloud-foundry-app-autoscaler-project-has-graduated\">auto-scaler<\/a> module.)<\/p>\n<p>Kubernetes has the benefit of an active open-source community that\u2019s continually expanding and building adjacent products. Interest in Kubernetes has grown rapidly over the past few years, a trend that\u2019s not been shared by CloudFoundry. The generic approach taken by Kubernetes makes it a more broadly applicable <a href=\"https:\/\/buradabiliyorum.com\/en\/category\/technology\/\" data-internallinksmanager029f6b8e52c=\"4\" title=\"Technology\" target=\"_blank\" rel=\"noopener\">technology<\/a>, in turn encouraging its adoption. You\u2019ll find it easier to hire skilled Kubernetes engineers as there are more of them out there.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-15639\" data-pagespeed-lazy-src=\"https:\/\/www.cloudsavvyit.com\/p\/uploads\/2022\/02\/40f64b6b.png?trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"\" width=\"1268\" height=\"648\" src=\"\/pagespeed_static\/1.JiBnMqyl6S.gif\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><\/p>\n<p>Kubernetes has an extensible architecture where you bring exactly what you need. You\u2019re free to replace components in your Kubernetes distribution and add <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/extend-kubernetes\/api-extension\/custom-resources\">new fundamental resource types for use<\/a> in your deployments. This keeps you in control of your application\u2019s architecture and leaves your infrastructure accessible and open to change.<\/p>\n<p>CloudFoundry is a highly opinionated solution that does most of the hard work for you; this accelerates initial deployment but gives you less opportunity to replace components, add overrides, and evolve your strategy over time. Once you\u2019ve chosen CloudFoundry, you need to settle in to its way of working to continue to realize its benefits. Kubernetes places fewer restrictions on what your infrastructure looks like. It can be readily adapted to suit highly specialized environments.<\/p>\n<h2 id=\"deployment-models\"><span class=\"ez-toc-section\" id=\"Deployment_Models\"><\/span>Deployment Models<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>You can see the application vs container model in practice by looking at how deployments actually work in the two different platforms. Here\u2019s an equivalent basic deployment made first to CloudFoundry and then Kubernetes.<\/p>\n<h3 id=\"cloudfoundry\"><span class=\"ez-toc-section\" id=\"CloudFoundry\"><\/span>CloudFoundry<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>With CloudFoundry you <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/docs.cloudfoundry.org\/cf-cli\/install-go-cli.html\">install the <code>cf<\/code> CLI<\/a>, head to your working directory, and run the following command:<\/p>\n<pre>cf push my-app<\/pre>\n<p>This will build and deploy your project using the CloudFoundry instance your CLI is authenticated to. The application will be named <code>my-app<\/code>. CloudFoundry will detect your source code type, acquire the appropriate buildpacks, build your application, and launch it into your cloud infrastructure.<\/p>\n<p>Deployments are configured with a simple YAML file called <code>manifest.yml<\/code>:<\/p>\n<div class=\"wp-geshi-highlight-wrap5\">\n<div class=\"wp-geshi-highlight-wrap4\">\n<div class=\"wp-geshi-highlight-wrap3\">\n<div class=\"wp-geshi-highlight-wrap2\">\n<div class=\"wp-geshi-highlight-wrap\">\n<div class=\"wp-geshi-highlight\">\n<div class=\"yaml\">\n<pre class=\"de1\"><span class=\"co4\">applications<\/span>:<span class=\"co3\">\n  - name<\/span><span class=\"sy2\">: <\/span>my-app<span class=\"co3\">\n    instances<\/span><span class=\"sy2\">: <\/span>4<span class=\"co4\">\n    env<\/span>:<span class=\"co3\">\n      EXAMPLE_VARIABLE<\/span><span class=\"sy2\">: <\/span>example<\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<p>Running <code>cf push<\/code> against a directory with this manifest would deploy four replicas of your app. The <code>EXAMPLE_VARIABLE<\/code> variable will be accessible from your source code.<\/p>\n<h3 id=\"kubernetes\"><span class=\"ez-toc-section\" id=\"Kubernetes\"><\/span>Kubernetes<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>As Kubernetes works with containers, you need an image for your app before you can get started. You\u2019ll have to write a Dockerfile and use <code>docker build<\/code> to build it:<\/p>\n<pre>docker build -t my-app:latest .<\/pre>\n<p>Once you\u2019ve got your image, you can write a set of Kubernetes manifests that describe the objects to create in your cluster:<\/p>\n<div class=\"wp-geshi-highlight-wrap5\">\n<div class=\"wp-geshi-highlight-wrap4\">\n<div class=\"wp-geshi-highlight-wrap3\">\n<div class=\"wp-geshi-highlight-wrap2\">\n<div class=\"wp-geshi-highlight-wrap\">\n<div class=\"wp-geshi-highlight\">\n<div class=\"yaml\">\n<pre class=\"de1\"><span class=\"co3\">apiVersion<\/span><span class=\"sy2\">: <\/span>apps\/v1<span class=\"co3\">\nkind<\/span><span class=\"sy2\">: <\/span>Deployment<span class=\"co4\">\nmetadata<\/span>:<span class=\"co3\">\n  name<\/span><span class=\"sy2\">: <\/span>my-app<span class=\"co4\">\nspec<\/span>:<span class=\"co3\">\n  replicas<\/span><span class=\"sy2\">: <\/span>4<span class=\"co4\">\n  selector<\/span>:<span class=\"co4\">\n    matchLabels<\/span>:<span class=\"co3\">\n      app<\/span><span class=\"sy2\">: <\/span>my-app<span class=\"co4\">\n  template<\/span>:<span class=\"co4\">\n    metadata<\/span>:<span class=\"co4\">\n      labels<\/span>:<span class=\"co3\">\n        app<\/span><span class=\"sy2\">: <\/span>my-app<span class=\"co4\">\n    spec<\/span>:<span class=\"co4\">\n      containers<\/span>:<span class=\"co3\">\n        - name<\/span><span class=\"sy2\">: <\/span>my-app-container<span class=\"co3\">\n          image<\/span><span class=\"sy2\">: <\/span>my-app:latest<span class=\"co4\">\n          env<\/span>:<span class=\"co3\">\n            - name<\/span><span class=\"sy2\">: <\/span>EXAMPLE_VARIABLE<span class=\"co3\">\n              value<\/span><span class=\"sy2\">: <\/span><span class=\"st0\">\"example\"<\/span><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<p>This manifest creates a deployment of the <code>my-app:latest<\/code> container image that will run four replicas concurrently. It also sets the <code>EXAMPLE_VARIABLE<\/code> environment variable, making it available within the running containers.<\/p>\n<p>Now you can <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/kubernetes.io\/docs\/reference\/kubectl\/overview\">use Kubectl<\/a>, the Kubernetes CLI, to launch your container instances into your connected cluster:<\/p>\n<pre>kubectl apply -f manifest.yml<\/pre>\n<p>These two minimal deployment examples illustrate the differences in concept, workflow, and developer experience between the two technologies. CloudFoundry\u2019s automated build procedures result in a friction-less deployment experience that\u2019s easily configured with CLI flags or a simple YAML file.<\/p>\n<p>Kubernetes tasks you with building your application\u2019s components into container images, then defining how they should run in your cluster. You need much more upfront configuration which is partly responsible for Kubernetes\u2019 reputation of being complex and challenging to learn. Persevering rewards you with the ability to exactly craft your infrastructure around your application; with CloudFoundry, you can end up adapting your app to work within the constraints of the platform.<\/p>\n<h2 id=\"the-overlap\"><span class=\"ez-toc-section\" id=\"Using_Both_Platforms\"><\/span>Using Both Platforms<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The two technologies don\u2019t exist in completely separate silos. It\u2019s possible to run <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/github.com\/cloudfoundry\/cf-for-k8s\">CloudFoundry <em>on<\/em> Kubernetes<\/a>, a model where the platform launches workloads into the Kubernetes cluster it is itself deployed to.<\/p>\n<p>In Kubernetes containers are the basic unit. This creates an expectation that you\u2019ll accept responsibility for building and supplying container images for your workloads. CloudFoundry\u2019s application-level model is a higher concept which layers in additional abstractions to build and prepare deployments for you. These are two distinct strategies that can both add value to the development experience depending on what you\u2019re creating.<\/p>\n<p>Combining the technologies can be a viable approach that lets you access the unique advantages of them both. You can use CloudFoundry for straightforward applications that work with standardized infrastructure. Projects which require a more bespoke system could be deployed straight to the underlying Kubernetes cluster, unlocking the flexibility of self-managed infrastructure.<\/p>\n<h2 id=\"conclusion\"><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>CloudFoundry and Kubernetes are two cloud-native platforms vying for the attention of developers and operations teams. Which you should choose depends on the app you\u2019re building, how much manual control you want over your infrastructure, and your long-term objectives for your service.<\/p>\n<p>CloudFoundry is a great way to quickly deploy any application without having to think about infrastructure components. Most apps \u201cjust work\u201d after a single <code>cf push<\/code>, drastically reducing the initial set up time and learning curve compared to Kubernetes. You don\u2019t need to think about maintaining infrastructure over time or updating pieces of your stack: if your source code builds successfully, it can be deployed to CloudFoundry.<\/p>\n<p>Kubernetes puts you closer to your infrastructure. You\u2019re responsible for mapping your system\u2019s architecture and determining the components you need for a successful deployment. This takes time and means you need to learn Kubernetes concepts and abstractions before you can begin. The benefit is increased flexibility and the option of creating infrastructure that more precisely matches your application\u2019s requirements.<\/p>\n<p>CloudFoundry is best when you want the highest level of automation and an opinionated design. It facilitates rapid deployments of large applications in a consistent and reproducible manner. CloudFoundry apps require relatively little maintenance over time, allowing them to be managed by smaller operations teams. Conversely Kubernetes is a more burdensome maintenance requirement but has become the standard for running heavily containerized systems in production. It\u2019s the right choice when you need customization, flexibility, and clear visibility into your infrastructure components.\n<\/p><\/div>\n<blockquote><p><strong><span style=\"color: #ff6600;\">If you liked the article, do not forget to share it with your friends. Follow us on\u00a0<span style=\"color: #ff0000;\"><a style=\"color: #ff0000;\" href=\"https:\/\/news.google.com\/publications\/CAAqBwgKMLG0nwswvr63Aw\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Google News<\/a><\/span>\u00a0too, click on the star and choose us from your favorites.<\/span><\/strong><\/p><\/blockquote>\n<blockquote>\n<p style=\"text-align: center;\">For forums sites go to <span style=\"color: #ff9900;\"><a style=\"color: #ff9900;\" href=\"https:\/\/forum.buradabiliyorum.com\/\" target=\"_blank\" rel=\"noopener\">Forum.BuradaBiliyorum.Com<\/a><\/span><\/strong><\/p>\n<\/blockquote>\n<blockquote>\n<p style=\"text-align: center;\"><strong>If you want to read more like this article, you can visit our <span style=\"color: #ff9900;\"><a style=\"color: #ff9900;\" href=\"https:\/\/en.buradabiliyorum.com\/technology\/\" target=\"_blank\" rel=\"noopener\">Technology category.<\/a><\/span><\/strong><\/p>\n<\/blockquote>\n<p><span style=\"color: black;\"><a style=\"color: #ff9900;\" href=\"https:\/\/www.cloudsavvyit.com\/15629\/cloudfoundry-vs-kubernetes-which-cloud-platform-should-you-choose\/\" target=\"_blank\" rel=\"noopener\">Source<\/a><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;Which Cloud Platform Should You Choose? \u2013 CloudSavvy IT&#8221; CloudFoundry and Kubernetes are two open-source technologies used to run applications in the cloud. Selecting the right platform for your deployments is an important choice to maximize performance, maintainability, and the productivity of your developers. In this article we\u2019ll compare the characteristics of both CloudFoundry and&#8230;<\/p>\n","protected":false},"author":1,"featured_media":414313,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/www.cloudsavvyit.com\/p\/uploads\/2022\/02\/8b2ff6c7.jpg","fifu_image_alt":"","footnotes":""},"categories":[18],"tags":[],"class_list":["post-414312","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts\/414312","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/comments?post=414312"}],"version-history":[{"count":0,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts\/414312\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/media\/414313"}],"wp:attachment":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/media?parent=414312"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/categories?post=414312"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/tags?post=414312"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}