This perspective paper introduces a novel framework for container orchestration called CODECO. The CODECO orchestration framework relies on a data-network-computing approach to define the best infrastructure that can support the operation of next-generation Internet applications across a mobile, heterogeneous Edge-Cloud continuum. The selection of such an infrastructure is aligned with target performance profiles defined by the user, such as resilience or greenness. CODECO proposes to rely on decentralized Artificial Intelligence approaches in an attempt to provide the most suitable infrastructure to an application deployment, considering infrastructural challenges, such as intermittent connectivity and node failure. This paper explains the current CODECO framework and provides insight into operational use-cases where CODECO is being deployed, as relevant examples of application for such a framework. Recent developments in the creation of the open-source CODECO framework are described and explained, allowing the use of the framework by the research community. The paper then provides a thorough analysis of CODECO’s features in comparison with existing orchestration frameworks, explaining the benefits introduced with this dynamic orchestration approach.
Big Data is a phenomenon that affects today’s world, with new data being generated every second. Today’s enterprises face major challenges from the increasingly diverse data, as well as from indexing, searching, and analyzing such enormous amounts of data. In this context, several frameworks and libraries for processing and analyzing Big Data exist. Among those frameworks Hadoop MapReduce, Mahout, Spark, and MLlib appear to be the most popular, although it is unclear which of them best suits and performs in various data processing and analysis scenarios. This paper proposes EverAnalyzer, a self-adjustable Big Data management platform built to fill this gap by exploiting all of these frameworks. The platform is able to collect data both in a streaming and in a batch manner, utilizing the metadata obtained from its users’ processing and analytical processes applied to the collected data. Based on this metadata, the platform recommends the optimum framework for the data processing/analytical activities that the users aim to execute. To verify the platform’s efficiency, numerous experiments were carried out using 30 diverse datasets related to various diseases. The results revealed that EverAnalyzer correctly suggested the optimum framework in 80% of the cases, indicating that the platform made the best selections in the majority of the experiments.
21 April 2026 in Future Generation Computer Systems
IoT monitoring systems, from traffic and pedestrian sensing in smart cities to building energy metering and industrial robot telemetry, increasingly run as containerised microservices on Kubernetes (K8s) clusters that span constrained edge nodes and cloud servers. Cognitive orchestration layers extend K8s with network-, data- and energy-aware placement, running on the same nodes as the monitoring workloads they manage, with their own footprint rarely reported. This paper proposes a component-level cost-attribution methodology and an automation-footprint trade-off analysis that relates the manual interventions removed to deployment latency, CPU, memory and estimated power consumed by each of its functional roles. We apply it to Cognitive Decentralised Edge–Cloud Orchestration (CODECO), an open-source cognitive orchestration framework, across six infrastructures, including three operational IoT deployments, ARM and x86 hardware, and vanilla K8s, K3s and KinD. The automated CODECO and CODEF workflow reduces the number of manual interventions from 72 to 9 (87.5%) under our action-count definition, with a total of 4.57 GB memory overhead, the most significant observed trade-off. Decomposing these costs by architectural layer reveals that within the tested cluster sizes, the installation time of the scheduling component shows no measurable growth and that of the learning component grows slowly, while cross-layer network management contributes the largest share of installation time and idle CPU consumption. Results show that orchestration costs arise in different architectural layers, indicating they can be placed and optimised independently without sacrificing automation benefits.