Fig 1 - uploaded by Nane Kratzke
Content may be subject to copyright.
Download
View publication
Deployment options and transferability opportunities: taken from [17]

Deployment options and transferability opportunities: taken from [17]

Source publication
Fig. 1. Deployment options and transferability opportunities: taken...
Fig. 3. The conceptual data model: The relation to descriptive cluster...
Table 3 . Common multi-cloud requirements and contributing elastic...
Fig. 4. Execution pipeline
+2 Fig. 5. Launching and terminating times (Kubernetes): The Kubernetes...
About the Complexity to Transfer Cloud Applications at Runtime and how Container Platforms can Contribute?
Preprint
Full-text available
  • Oct 2018
Cloud-native applications are often designed for only one specific cloud infrastructure or platform. The effort to port such kind of applications into a different cloud is usually a laborious one time exercise. Modern Cloud-native application architecture approaches make use of popular elastic container platforms (Apache Mesos, Kubernetes, Docker S...
Cite
Download full-text

Context in source publication

Context 1
... this point this should make the general idea clear. All the details will be explained in more details in Section 4 and further multi-cloud options like public cloud exits, cloud migrations, public multi-clouds, hybrid clouds, overflow processing and further can be handled using the same approach (see Figure 1). ...

Similar publications

Data Science as a Service - Prototyping an Integrated and Consolidated IT Infrastructure Combining Enterprise Self-Service Platform and Reproducible Research
Preprint
  • Jun 2020
A data scientific process (e.g., Obtain, Scrub, Explore, Model, and iNterpret (OSEMN)) usually consists of different steps and can be understood as an umbrella for the combination of different most modern techniques and tools for the extraction of information and knowledge. When developing a suitable IT infrastructure for a self-service platform in...
View