1、 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.ARC332-SFrank MancinaVP of Engineering&OperationsHAProxy TechnologiesJakub SuchyDirector of Soluti
2、ons EngineeringHAProxy TechnologiesBeyond Multi-Cloud Chaos:The Unified Cloud Mesh Architecture“Service Mesh wasdesigned to solve connectivity”For most organizations,it simply shifted the complexity |Booth#1179The Fractured EnterpriseThe modern enterprise wasnt built;it evolved.Its a fractured digit
3、al landscape:multiple clouds/regionson-prem data centers legacy applicationsMost service meshes werent built with this in mind.They struggle to integrate the“brownfield |Booth#1179Sidecar architecture becomes too expensive and complex as you scaleS3S1S2S5Namespace 2ServiceS1S4S3S2Namespace NServiceS
4、3S1S2S5Namespace 2ServicePodsS1S4S3S2Namespace NServicePodsS1S4S5S2Namespace 1ServicePodsS1S4S5S2Namespace 1ServicePodsPodsPodsWorker node 1Worker node NK8s Cluster A/Region A No service meshS3S1S2S5Namespace 2ServiceS1S4S3S2Namespace NServiceS3S1S2S5Namespace 2ServicePods+SidecarsS1S4S3S2Namespace
5、NServicePods+SidecarsS1S4S5S2Namespace 1ServicePods+SidecarsS1S4S5S2Namespace 1ServicePods+SidecarsPods+SidecarsPods+SidecarsWorker node 1Worker node NK8s Cluster A/Region A SidecarWorker node 1S1S4S5S2Namespace 1ServicePods+SidecarsThe Mesh TaxThe Mesh TaxSidecar-less architecture is better,however
6、 complexity shifted to distributed components:Layer 4 proxy per node+Layer 7 proxy per namespace or service accountWorker node 1K8s Cluster A/Region A Sidecar-lessS1S4S5S2Namespace 1ServicePodsLayer 7 proxyS3S1S2S5Namespace 2ServicePodsLayer 7 proxyS1S4S3S2Namespace nServicePodsLayer 7 proxyLayer 4