Intelligent Tech Channels Issue 55 | Page 16

But what else do we need to know about how hybrid multi-cloud happened and how this technology should be most productively implemented today ?


Rob Tribe , VP , System Engineering EMEA at Nutanix , discusses how best to utilise hybrid multi-cloud solutions .

Throughout the rapid evolution of cloud computing from its earliest stages , we have witnessed the development and extension of many different cloud service specialisms , applications and optimisations . But however diverse and complex the cloud becomes , we can classify its core DNA into two strands i . e . public and private .

With public cloud services coming from data centres and offering maximum flexibility , breadth and scope , private or on-premises cloud sits alongside the public cloud in a sort of yin-yang balance to provide control , privacy and compliance where needed . Businesses quickly realised that a hybrid combination of the two strands was the most prudent workable approach .
When these same businesses also saw that they could cover a wider multiplicity of use cases and deployment requirements by extending hybrid across multiple Cloud Services Providers ( CSPs ), we reached the point of hybrid multi-cloud epiphany that characterises the most progressive cloud implementations today .
Core validations
Among the core validation points that exist for hybrid multi-cloud are the need to locate certain workloads in specific geographic locations .
This can be due to latency requirements if a particular application ’ s functionality depends upon it working to a precise number of microseconds , or it can be in order to fulfil upon regulatory compliance rulings and legislation . Potentially , it can be as a result of both .
While these requirements can theoretically be delivered from the public cloud , in the vast majority of scenarios these reasons are core justifications for the workloads concerned being located on-premises in private cloud deployments .
CAPEX to OPEX in public cloud
For applications that use a lot of compute resources but on a highly variable basis and only for a short burst of time , on-premises private cloud represents a disproportionate Capital Expenditure ( CAPEX ) outlay with the risk of purchased resources lying idle and unused .
A good example here might be quarterly or annual tax processing ; the workload is high and heavy , but essentially intermittent on a comparatively date-specific basis . Running this type of workload in the public cloud enables us to shoulder a cost that specifically tracks the consumption of resources , which is logically an Operational Expenditure ( OPEX ) weighted use case best suited to the public cloud .
Straddling the colocation intersection point
Looking at the middle ground and looking for the deployment sweet spot , we need to think about what happens if we start a new
16 www . intelligenttechchannels . com