{"id":269146,"date":"2023-09-11T12:33:36","date_gmt":"2023-09-11T17:33:36","guid":{"rendered":"https:\/\/www.webscale.com\/?p=269146"},"modified":"2023-12-29T15:30:53","modified_gmt":"2023-12-29T20:30:53","slug":"roadmap-to-the-adaptive-edge-balancing-cost-efficiency-usability-and-performance-tradeoffs","status":"publish","type":"post","link":"https:\/\/www.webscale.com\/blog\/roadmap-to-the-adaptive-edge-balancing-cost-efficiency-usability-and-performance-tradeoffs\/","title":{"rendered":"Roadmap to the Adaptive Edge \u2013 Balancing Cost Efficiency, Usability, and Performance Tradeoffs"},"content":{"rendered":"

The network edge presents new challenges in optimizing application deployments, as the deeper an application is pushed into the internet, the greater the associated costs to run those workloads. As part of Kubernetes on EDGE Day at KubeCon + CloudNativeCon event in Europe, Webscale shared a set of optimization considerations and strategies that allow workloads to be as close to users as possible, bounded by a business value construct. At the same time, we discussed the importance of maintaining simplicity in the usability of the system, so that developers can specify how deeply they want their application to run without overallocation of resources.<\/span><\/i><\/p>\n

This blog post presents an excerpt from Webscale\u2019s presentation, discussing the use of Cloud Native Computing Foundation (CNCF) core technologies, including Kubernetes and Prometheus as a base, to establish a framework for evaluating projects within the CNCF landscape and their suitability for edge use cases. The session also examined Kubernetes Federation techniques, multi-cluster orchestration systems, and traffic direction and service discovery strategies against a selection criterion to assist architects in making \u201cgood-fit\u201d decisions.<\/span><\/p>\n

Building the Roadmap: Where to Start<\/b><\/h3>\n

When we talk about balancing performance against cost, we\u2019re talking about running hundreds of instances of an application at the edge to deliver, on average, shorter distance, lower latency, fewer dropped shopping carts, and so on. But there\u2019s a cost associated with that \u2013 not just in terms of cycles, but in terms of operating all those clusters.<\/span><\/p>\n

While you might love to run clusters everywhere, the cost is likely too high for that to be a realistic option. So, how do you get the effect of running everywhere without actually running everywhere? First, let\u2019s establish our bearings by considering some of the \u201cwhat ifs\u201d at play and of note:<\/span><\/p>\n