## 6 Genericity: Quantitative Analysis
Supported workloads 4. Reusable container configuration 5. Service upgrades 6. Resource quota management 7. Improved security isolation For all 7 sub-aspects, the open-source distribution of Kubernetes supports all common features of these sub-aspects. As such Kubernetes is very generic with respect to these sub-aspects. * Docker Swarm integrated mode has the most features for 3 sub-aspects: 1. Services networking 2. Host ports conflict management 3. Cluster network security For the first two sub-aspects, Docker Swarm integrated mode offers support for all common features, while for the last sub-aspect, the open-source distribution of Docker Swarm integrated mode offers support for all common features except _authorization of CO agents on worker nodes_. * DC/OS has the most features for 2-sub-aspects: 1. Cluster maintenance 2. Multi-cloud deployments For the first sub-aspect, DC/OS offers support for all common features of this sub-aspect by building upon Mesos and Marathon and providing detailed manual instructions for upgrading DC/OS. For the second sub-aspect, DC/OS offers support for all common features except _recovery from network partitions_. * Mesos has the most features for 1 sub-aspect: 1. Persistent volumes After all, Mesos offers support for both Docker volumes as well as CSI-based volumes. There are furthermore tied observations between Docker Swarm, Kubernetes and DC/OS for 12 sub-aspects where these CO frameworks offer an equal number of features (see Figure 8 for a visual overview of the differences in genericity between these frameworks for the 27 sub-aspects). _RQ6b. Which functional sub-aspects are best supported by a CO framework in terms of common features and unique features?_ Kubernetes clearly offers the highest number of unique features (see Figure 5). When adding up common and unique features, Kubernetes even supports the highest number of features for all 9 aspects (see Figure 9). We argue that it is fair to take into account the large number of unique features of Kubernetes when ranking CO frameworks with respect to genericity. After all, as already stated in Section 1, both Docker EE and DC/OS also offer support for Kubernetes as an alternative orchestrator. So the unique features are not a source of vendor lock-in. Table 6 provides an overview of the total number of features per (sub)-aspect and per CO framework. In comparison to the quantitative analysis of the common features only (i.e., RQ6a), we find a more significant difference in ranking between the frameworks when re-applying the Friedman test for unreplicated designs (\(p\)-value = 1.729 \(\times\) 10-10). However, a pairwise comparison between CO frameworks using the Nemenyi test [56] did not show any significant differences between the three major frameworks Docker Swarm integrated mode, Kubernetes and DC/OS. We do observe an additional, significant difference between Docker Swarm integrated mode and Docker Swarm stand-alone. This can be explained by the fact that the former introduces more unique features than the latter. However, for 17 sub-aspects there is a specific CO framework that supports the highest number of common and unique features. We graphically present the top 3 CO frameworks using a radar chart (see Figure 10). Kubernetes offers the most features for 15 sub-aspects. Docker Swarm integrated  
Figure 8: Radar chart of Docker Swarm integrated mode, Kubernetes and DC/OS to graphically present in which sub-aspects these CO frameworks support the highest number of common features. Figure 9: The total number of features supported by each of the CO frameworks is shown for the 9 aspects. mode loses the 1 st rank for the sub-aspect \"cluster network security\" to Kubernetes, but still offers the most features for the sub-aspects \"services networking\" and \"host port conflict management\". Mesos does not offer anymore the most features for the sub-aspect \"persistent volumes\", which is now more elaborately supported by Kubernetes. Instead, it offers the most features for the sub-aspect \"allocation of other resources\".