{"id":5186,"date":"2022-01-06T08:00:03","date_gmt":"2022-01-06T16:00:03","guid":{"rendered":"https:\/\/www.www.pogolinux.com\/blog\/?p=5186"},"modified":"2022-02-01T09:01:11","modified_gmt":"2022-02-01T17:01:11","slug":"composability-versus-virtualization","status":"publish","type":"post","link":"https:\/\/www.pogolinux.com\/blog\/composability-versus-virtualization\/","title":{"rendered":"Data Center Strategy: Composability vs. Virtualization"},"content":{"rendered":"<p>Based on continually changing business and IT needs, <a href=\"https:\/\/www.pogolinux.com\/blog\/why-composable-infrastructure-future-data-center\/\">composable infrastructure is emerging<\/a> as a category of infrastructure aimed at optimizing an organization&#8217;s IT resources to improve business agility and responsiveness.<\/p>\n<p>Composable infrastructure is the ability to connect compute, GPU, storage and networking into <em>pools of resources<\/em>\u00a0that are <em>provisioned through software APIs<\/em> and network fabric, then <em>deployed into bare-metal server nodes. <\/em>In composable infrastructure environments, hardware resources can be composed into exact-sized system designs (including bare-metal) for each private cloud hosted application&#8217;s workload needs. This infrastructure architecture approach is similar to a public cloud where resource capacity is requested and provisioned from shared capacity \u2013 except composable infrastructure sits behind a corporate firewall on-premises in an organization&#8217;s data center.<\/p>\n<p>This focus on provisioning hardware into available compute, storage and networking resources, reduces underutilization and overprovisioning while creating a more flexible and agile data center. The approach of composability is similar to a public cloud in that hardware resources are requested and provisioned from shared capacity \u2013 except a software-defined composable infrastructure sits on-premises in an organization&#8217;s data center.<\/p>\n<p>Previously, we covered <a href=\"https:\/\/www.pogolinux.com\/blog\/what-is-composable-infrastructure\/\">what is composable infrastructure<\/a> and <strong>how organizations can benefit from composability.<\/strong> Next, let&#8217;s review how this approach is different from deploying virtualized data center environments.<\/p>\n<p><em>Choosing between software-defined architectures? Here&#8217;s what data center administrators need to know to compare composable infrastructure vs. virtualization or container-based infrastructure. Questions? Drop us an email at <a href=\"mailto:sales@www.pogolinux.com\">sales@www.pogolinux.com<\/a><\/em><\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_89 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" 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: #999;color:#999\" 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><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.pogolinux.com\/blog\/composability-versus-virtualization\/#Composability_vs_Virtualization_Containerization\" >Composability vs. Virtualization &amp; Containerization<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.pogolinux.com\/blog\/composability-versus-virtualization\/#Compare_Composability_vs_Virtualization\" >Compare Composability vs. Virtualization<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.pogolinux.com\/blog\/composability-versus-virtualization\/#Liqid_Composable_Infrastructure\" >Liqid Composable Infrastructure<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.pogolinux.com\/blog\/composability-versus-virtualization\/#Choosing_the_Right_Composable_Infrastructure_Solution\" >Choosing the Right Composable Infrastructure Solution<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.pogolinux.com\/blog\/composability-versus-virtualization\/#Setting_up_a_Composability_Proof_of_Concept\" >Setting up a Composability Proof of Concept<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Composability_vs_Virtualization_Containerization\"><\/span>Composability vs. Virtualization &amp; Containerization<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Fundamentally, virtualization and containerization is the opposite of composable infrastructure framework. Take the visual diagram of a glass of orange juice: In virtualization or containerization, orange juice is provisioned to give multiple users the appearance that several glasses of orange juice are available.<\/p>\n<p>Based on requirements, each user has access to resources without the ability to exceed capacity, nor return underutilized resources during off-peak hours for other users. As a result, virtualization and containerization are great to share a single server and support many users with small enough needs, but not an optimal framework to maximize resource utilization.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-5387 size-full alignleft\" src=\"https:\/\/www.pogolinux.com\/blog\/wp-content\/uploads\/2020\/12\/21-Q1-blog-article_composability-versus-virtualization.jpg\" alt=\"\" width=\"725\" height=\"400\"><\/p>\n<h3><\/h3>\n<h3><\/h3>\n<h3><\/h3>\n<h3><\/h3>\n<h3><\/h3>\n<h3><\/h3>\n<h3><\/h3>\n<h3><\/h3>\n<h3><\/h3>\n<h3><\/h3>\n<h3><span class=\"ez-toc-section\" id=\"Compare_Composability_vs_Virtualization\"><\/span>Compare Composability vs. Virtualization<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The root of composability is the opposite approach of virtualization\/containerization: the individual components of a glass of orange juice that make up the whole \u2013 the orange juice, straw, slices of orange \u2013 are disaggregated into a virtual whole. In composability, a glass of orange juice is customized for each user&#8217;s unique requirements by taking individual components, such as the orange juice, 2 straws, 5 slices of orange.<\/p>\n<p>The API management software orchestrates the provisioning of the resource pools by composing bare-metal environments \u2013 not virtual environments with a hypervisor layer. The hardware elements are separated \u2013 CPU\u2019s, NVMe SSD\u2019s, GPU\u2019s, NIC\u2019s and FPGA \u2013 and independently assigned into server nodes. Based on hosted application requirements, components can be scaled-up or down, as needs change.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Liqid_Composable_Infrastructure\"><\/span>Liqid Composable Infrastructure<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>While virtualization can handle the majority of applications in use today, the need for bare-metal or single host operations still exists. Hyperconverged relies heavily on virtualization and doesn&#8217;t typically lend itself to bare-metal applications. An architecture with a pool of available compute resources and the ability to assign specific workloads is much more conducive to this type of requirement.<\/p>\n<p>Liqid composable infrastructure is hypervisor agnostic and optimized for VMWare\u2019s VSAN, Dell VXRail, and other leading providers. The ability to create multiple servers on demand with composable software reduces the number of licenses required for virtualization deployments. Liqid composable software also ensures complete fault tolerance, instantly transferring data from failed compute nodes to other available disaggregated hardware.<\/p>\n<p>Disaggregated pools of GPUs, FPGAs, CPUs, NVMe SSDs, and Intel Optane&#x2122; memory can now be added at will and utilized as shared resources in quantities that correspond to the needs of a given workload or task, while hypervisors such as VSAN can dictate resource allocation via Liqid APIs, extending the life of existing hardware and allowing IT organizations to grow infrastructure as required.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Choosing_the_Right_Composable_Infrastructure_Solution\"><\/span>Choosing the Right Composable Infrastructure Solution<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The ability to accelerate time-to-market for digital products, or improve service-levels and project delivery times, is a competitive advantage that\u2019s necessary for any data-driven organization. A comprehensive software-defined composable infrastructure framework can providers data center admins the ability to configure, manage and scale out physical bare-metal server systems in seconds.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Setting_up_a_Composability_Proof_of_Concept\"><\/span>Setting up a Composability Proof of Concept<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Hosted applications will drive future adoption of composable infrastructure, and proof of concepts (POC&#8217;s) are the best way to evaluate a composability investment against a virtualized or containerized environment. More often than not, the right solution for your data center is a mix of composability alongside a static architecture to experience the greatest platform flexibility, scalability, and unit economics.<\/p>\n<p>IT decision makers should lay out rigorous performance, resiliency and scalability requirements. Additionally, knowledge of the hosted application requirements is necessary to ensure a POCs provide clear, decisive results. To objectively measure technology and operational benefits, it&#8217;s possible to start small and build out as you go. Most vendors composable infrastructure will happily help you set up a proof-of-concept solution to test out the design set-up that best meets your needs.<\/p>\n<p>If you&#8217;d like to learn more about how to maximize your data center infrastructure by up to 90% while minimizing its footprint, give us a call at <strong>(888) 828-7646<\/strong>, email us at <a href=\"mailto:sales@www.pogolinux.com\">sales@www.pogolinux.com<\/a> or <a href=\"https:\/\/www.pogolinux.com\/blog\/book-meeting\/\">book a time calendar<\/a> to speak. We&#8217;ve helped organizations of all sizes deploy composable solutions for just about every IT budget.<\/p>\n<p><a href=\"https:\/\/www.pogolinux.com\/products\/composable-infrastructure\/overview\" target=\"_blank\" rel=\"noopener noreferrer\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-5753 size-full\" src=\"https:\/\/www.pogolinux.com\/blog\/wp-content\/uploads\/2021\/01\/blog-article-footer_composable-infrastructure.jpg\" alt=\"\" width=\"725\" height=\"198\"><\/a><\/p>\n<p><script charset=\"utf-8\" type=\"text\/javascript\" src=\"\/\/js.hsforms.net\/forms\/shell.js\"><\/script><br \/>\n<script>\n  hbspt.forms.create({\n\tregion: \"na1\",\n\tportalId: \"5988479\",\n\tformId: \"0015f2c7-3f98-4b70-98a8-8abf1e36333b\"\n});\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Based on continually changing business and IT needs, composable infrastructure is emerging as a category of infrastructure aimed at optimizing an organization&#8217;s IT resources to improve business agility and responsiveness. Composable infrastructure is the ability to connect compute, GPU, storage and networking into pools of resources\u00a0that are provisioned through software APIs and network fabric, then&#8230;<\/p>\n","protected":false},"author":6,"featured_media":5536,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[251,250],"tags":[],"class_list":["post-5186","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-liqid","category-composable-infrastructure"],"_links":{"self":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts\/5186","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/comments?post=5186"}],"version-history":[{"count":43,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts\/5186\/revisions"}],"predecessor-version":[{"id":5761,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts\/5186\/revisions\/5761"}],"wp:attachment":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/media?parent=5186"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/categories?post=5186"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/tags?post=5186"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}