# Infrastructure Engineering Published articles for Infrastructure Engineering. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## What Isn't A PaaS DevFeed: [What Isn't A PaaS]() Original publisher: [Read original article]() Author: Matt Butcher Published: 2025-01-06T12:00:00Z Content type: opinion Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [App](), [Tool](), [configuration]() Tags: [app](), [developers](), [infrastructure](), [infrastructure-engineering](), [tools]() ### AI overview The article argues that tools requiring developers to perform infrastructure engineering are not true PaaS offerings, because the promise of PaaS is deploying an app without additional infrastructure configuration. ### Source excerpt The promise of PaaS is that developers can build an app, and then deploy it without having to do any additional infrastructure configuration. But a few recent tools claim to be PaaS, yet force developers to do infrastructure engineering. These tools are not actually PaaSes. ## Cloud without Kubernetes DevFeed: [Cloud without Kubernetes]() Original publisher: [Read original article]() Author: Drew Published: 2024-02-12T18:58:13Z Content type: opinion Language: en Sources: [Brave New Geek]() Topics: [Kubernetes](), [Cloud](), [Serverless](), [migration](), [Google Cloud Platform (GCP)]() Tags: [cloud](), [cloud-native](), [cloud-run](), [devops](), [gcp](), [google-cloud](), [infrastructure-engineering](), [internal-developer-platform](), [kubernetes](), [migrations](), [ops](), [platform-engineering](), [product-development](), [serverless]() ### AI overview This opinion article questions whether Kubernetes is the right abstraction for every cloud workload. It describes organizations choosing serverless approaches instead, including a customer migrating an e-commerce platform to Google Cloud without Kubernetes, while noting concerns about workload fit, re-architecting, cost, and efficiency. ### Source excerpt I think it's safe to say Kubernetes has "won" the cloud mindshare game. If you look at the CNCF Cloud Native landscape (and manage to not go cross eyed), it seems like most of the projects are somehow related to Kubernetes. KubeCon is one of the fastest-growing industry events. Companies we talk to at Real Kinetic who are either preparing for or currently executing migrations to the cloud are centering their strategies around Kubernetes. Those already in the cloud are investing heavily in platform-izing their Kubernetes environment. Kubernetes competitors like Nomad, Pivotal Cloud Foundry, OpenShift, and Rancher have sort of just faded to the background (or simply pivoted to Kubernetes). In many ways, "cloud native" seems to be equated with "Kubernetes". ## Structuring a Cloud Infrastructure Organization DevFeed: [Structuring a Cloud Infrastructure Organization]() Original publisher: [Read original article]() Author: Neville Poole Published: 2020-12-07T17:21:46Z Content type: article Language: en Sources: [Brave New Geek]() Topics: [Cloud](), [cloud-infrastructure](), [DevOps](), [on-prem](), [Development]() Tags: [cloud](), [culture](), [developer-enablement](), [development](), [devops](), [engineering-culture](), [infrastructure](), [infrastructure-engineering](), [on-prem](), [ops](), [product-development](), [product-mindset]() ### AI overview The article discusses how companies moving from conventional on-premises IT organizations to cloud environments can structure their engineering organizations. It presents product development and infrastructure as distinct areas and notes that DevOps and cloud adoption do not eliminate their different roles. ### Source excerpt Real Kinetic often works with companies just beginning their cloud journey. Many come from a conventional on-prem IT organization, which typically looks like separate development and IT operations groups. One of the main challenges we help these clients with is how to structure their engineering organizations effectively as they make this transition. While we approach this problem holistically, it can generally be looked at as two components: product development and infrastructure. One might wonder if this is still the case with the shift to DevOps and cloud, but as we'll see, these two groups still play important and distinct roles.